In a CI/CD pipeline, if there's a changeset already created we may want to prevent stackmanager from creating another one as the first changeset may be pending review/approval. The current behavior is permissive and allows another changeset to be created.
This could be an option on the deploy command to fail if a changeset exists - possibly with multiple values so that it can continue if only failed changesets exist (as this might be the one that fixes it and we don't want to require manual clean-up).
If a changeset is rejected (e.g. an approval step is rejected in a CI/CD pipeline), it should be possible to delete the change-set and if the stack has not been created (REVIEW_IN_PROGRESS) and there are no remaining changesets, delete the stack.
In a CI/CD pipeline, if there's a changeset already created we may want to prevent stackmanager from creating another one as the first changeset may be pending review/approval. The current behavior is permissive and allows another changeset to be created.
This could be an option on the deploy command to fail if a changeset exists - possibly with multiple values so that it can continue if only failed changesets exist (as this might be the one that fixes it and we don't want to require manual clean-up).
If a changeset is rejected (e.g. an approval step is rejected in a CI/CD pipeline), it should be possible to delete the change-set and if the stack has not been created (REVIEW_IN_PROGRESS) and there are no remaining changesets, delete the stack.