Skip to content

fix: reconcile site UUID with config sync before config:import in suds:update - #5

Open
andycarlberg wants to merge 1 commit into
Bounteous-Inc:mainfrom
andycarlberg:fix/update-config-sync-uuid
Open

fix: reconcile site UUID with config sync before config:import in suds:update#5
andycarlberg wants to merge 1 commit into
Bounteous-Inc:mainfrom
andycarlberg:fix/update-config-sync-uuid

Conversation

@andycarlberg

Copy link
Copy Markdown

Summary

  • suds:update now reconciles the target site's system.site.uuid with the value recorded in the config sync directory before running config:import, mirroring how BLT handled this in its update/deploy flow.
  • Environments provisioned independently of the source database (e.g. a fresh site:install) get their own UUID, which previously caused config:import to fail with a UUID mismatch.

Test plan

  • Unit tests (UpdateCommandsTest) cover UUID reconciliation dispatch and the skip-when-unavailable case.
  • Integration tests (UpdateCommandsIntegrationTest) assert config:set system.site uuid dispatches in the correct order.
  • Functional test against a real SUT diverges the site UUID, runs suds:update, and confirms it's reconciled back to match config sync.
  • composer lint, composer analyze, and the full unit/integration/functional suites pass locally.

Fixes #1

…s:update

config:import fails when the target site's system.site.uuid diverges from
config/sync/system.site.yml, which happens on any environment provisioned
independently of the source database (e.g. a fresh install). suds:update
now sets the site's UUID to match config sync before importing, mirroring
how BLT handled this in its update/deploy flow.

Fixes Bounteous-Inc#1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

suds:update should set the target site's UUID to match config/sync before importing config

1 participant