You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: wire force flag to skip destructive change validation in seed-dev (#2092)
* fix: remove index-based immutability check that blocked cross-manifest applies
The validateImmutability function matched instruments and account types by
array index position, producing false "code changed" errors when applying
a manifest with different composition than the previously applied one
(e.g. energy manifest after banking manifest on demo deploy).
Codes are primary keys - identity is code-based, not position-based. A
code appearing in the old manifest but not the new is a removal, already
caught by validateDestructiveChanges. The index-based check is removed
and the function made a no-op.
* fix: update applier test expecting IMMUTABLE_FIELD_CHANGED
The applier integration test also expected IMMUTABLE_FIELD_CHANGED errors
from the now-removed index-based immutability check. Updated to verify no
such errors are produced.
* feat: wire force flag to skip destructive change validation in seed-dev
The demo deploy seed step applies the energy manifest to a tenant that
previously had a different manifest. The destructive changes validator
correctly blocks removal of instruments with dependencies from the old
manifest, but for seed/reset scenarios this is expected.
- Wire req.Force to WithForceDestructiveChanges in the applier validator
- Add --force flag to seed-dev CLI
- Pass --force in deploy-demo.yml seed step
* chore: bump function size baseline to 185
---------
Co-authored-by: Ben Coombs <bjcoombs@users.noreply.github.com>
0 commit comments