Add overrides testing in lifecycle integration tests #10752
Merged
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 allows specific changes to be tested on an existing cluster during an
update cluster --yes
and ensuring a subsequentupdate cluster
dryrun correctly reports no changes.To specify changes, create a
cluster.overrides.txt
orinstancegroup.<name>.overrides.txt
file in the update_cluster integration test's directory as demonstrated here.Each line is a field=value format, each batch of changes is separated by a
---
line.Each batch will be ran through
update cluster --yes
on its own.In particular, reverting #10742 correctly caused a panic, so these tests are now capable of exposing those types of bugs.