Filter by active stack when executing a cloudformation changeset #11384
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.
Motivation
This PR fixes the behaviour of the cloudformation api, when deleting and recreating a stack with the same name.
Now stacks which have the status
DELETE_COMPLETE
are filtered out when a changeset execution is requested for a stack, which closes #11333Changes
The
find_changeset
function instores.py
of the cloudformation package now accepts an additional optional parameteractive_only
which filters the stacks by their status when set. This parameter is set to true only inexecute_changeset
handler of the cloudformation provider.Testing
TODO
TODO
What's left to do: