Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create changeset for new stack #915

Open
dtlhlbs opened this issue Jul 2, 2020 · 2 comments
Open

Create changeset for new stack #915

dtlhlbs opened this issue Jul 2, 2020 · 2 comments
Labels
state: has pr

Comments

@dtlhlbs
Copy link

dtlhlbs commented Jul 2, 2020 •
edited

We'd like to create a changeset in our CI/CD pipeline before we execute it, so we can review changes and execute the change set manually. CloudFormation gives us the opportunity to deploy without executing via --no-execute-changeset, or to create a changeset with either CREATE or UPDATE --change-set-type. I don't think Sceptre has this ability? When we create a changeset for a stack that doesn't exist we get:

"An error occurred (ValidationError) when calling the CreateChangeSet operation: Stack [stack-name-goes-here] does not exist"

And launch doesn't have an equivalent to --no-execute-changeset.
@kirkhansen
Copy link

See issue #663. We were waiting on some scope clarification before proceeding.

@zaro0508
Copy link
Contributor

zaro0508 commented May 28, 2024 •
edited

it looks like the sceptre update command has a --change-set option, the sceptre doc says.. "Create a change set before updating". Does this not work?

alexharv074 added a commit to alexharv074/sceptre that referenced this issue Jun 1, 2024
@alexharv074
[Resolve Sceptre#915] Support ChangeSetType UPDATE
9a09303 
This adds logic supporting the case of creating change sets for a stack
that does not already exist, i.e. specifying ChangeSetType of CREATE.
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/cloudformation/client/create_change_set.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
state: has pr
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kirkhansen @craighurley @zaro0508 @dtlhlbs