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

Zero-alarm stacks are not updated #162

Closed
tomhaigh opened this issue Aug 20, 2018 · 0 comments
Closed

Zero-alarm stacks are not updated #162

tomhaigh opened this issue Aug 20, 2018 · 0 comments
Assignees
@tomhaigh
Labels
bug

Comments

@tomhaigh
Copy link
Contributor

tomhaigh commented Aug 20, 2018 •
edited
Loading

Watchman intentionally does not create CloudFormation stacks with zero alarms, because it would be silly. It does this by skipping the deploy of any stack that would have zero alarms.

However if you delete all the entries (deployable via CloudFormation) from your alerting group, you want it to perform that update. Currently it is skipped and alarms are left behind.

So the zero-alarm stack skipping should only be applied on create, not update.
@tomhaigh tomhaigh added the bug label Aug 20, 2018
@tomhaigh tomhaigh self-assigned this Aug 30, 2018
@tomhaigh tomhaigh changed the title Empty stacks are not updated Zero-alarm stacks are not updated Aug 30, 2018
@tomhaigh tomhaigh mentioned this issue Aug 30, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomhaigh tomhaigh

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomhaigh