Skip to content

Fixes issue with non-interactive changeset updates & stack policies#657

Merged
phobologic merged 1 commit into
masterfrom
fix_stack_policy_non_interactive_changesets
Sep 7, 2018
Merged

Fixes issue with non-interactive changeset updates & stack policies#657
phobologic merged 1 commit into
masterfrom
fix_stack_policy_non_interactive_changesets

Conversation

@phobologic

Copy link
Copy Markdown
Member

create change set doesn't allow a stack_policy argument like
create/update stack calls. This was handled in the interactive version,
but not in the non-interactive version.

Fixes #650

create change set doesn't allow a `stack_policy` argument like
create/update stack calls.  This was handled in the interactive version,
but not in the non-interactive version.

Fixes #650
'UPDATE', service_role=self.service_role, **kwargs
)

self.deal_with_changeset_stack_policy(fqn, stack_policy)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok cool, so this is the bug, you refactored the logic so you could call it here.

@ejholmes ejholmes left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was handled in the interactive version,
but not in the non-interactive version.

I didn't even realize we hit changesets in non-interactive. In what scenario is that possible? When a stack is protected?

@phobologic

Copy link
Copy Markdown
Member Author

@phobologic phobologic merged commit ed7ce1c into master Sep 7, 2018
@phobologic phobologic deleted the fix_stack_policy_non_interactive_changesets branch September 7, 2018 15:54
@nielslaukens

Copy link
Copy Markdown
Contributor

@ejholmes ChangeSets are required when a Transform is present, both on create & on update.

phrohdoh pushed a commit to phrohdoh/stacker that referenced this pull request Dec 18, 2018
…loudtools#657)

create change set doesn't allow a `stack_policy` argument like
create/update stack calls.  This was handled in the interactive version,
but not in the non-interactive version.

Fixes cloudtools#650
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants