Moved blocks and fix to resman for FAST v33-v34 transition #2541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a followup from #2512 and a simple way we should provide guidance on updating FAST for every release. The fast-test-05 org is pinned to last version, and running apply on bootstrap, resman, and net-a allows us to write moved blocks and note down major changes.
The release notes for v34 should add a section
FAST migration from v33.0.0 to v34.0.0
Bootstrap stage
No destructive changes. A few IAM bindings are reapplied cleanly.
Resource management stage
Network security IaC resources change names from
resman-netsec
toresman-nsec
and need recreation. Network security state should be transitioned to local before applying resource management, and re-transitioned to remote after refreshing resman output files and netsec provider.Project factory dev and prod resources will change internal names, the moved blocks in the provided file should seamlessly rename them in state.