Add support for CloudFormation Stack Termination Protection

[gabriellhrn]

CloudFormation now allows us to enable Stack Termination Protection, which works similar to the EC2 termination protection. We can enable it while creating the stack. When termination protection is enable, CloudFormation won't delete the stack unless we explicitly disable the protection. There are more information about this in the announcement.

[phobologic]

Thanks @gabriellhrn - can you give an idea of how you would expect this to work in stacker?

Would it be a configuration setting on a stack by stack basis?

Would you expect for stacker to have a way to automatically remove the protection if some command argument, etc, were provided?

What should stacker do if someone calls destroy and it hits a stack that is protected, yet --force was provided?

Thanks!

[gabriellhrn]

My idea is to add a new optional parameter in the stack configuration. If the parameter is set to True, we can then enable the termination protection using CloudFormation Stack Options when creating the CloudFormation Stack.

I think we could let the default behaviour be not to enable protection and we would have to enable it for each stack, as it is in CloudFormation.

Maybe we could disable it when the option is changed from True to False in the stack configuration or in the event destroy is called with --force.

Those are my thoughts on it. What do you think, @phobologic?

Thanks.

[phobologic]

Thanks @gabriellhrn - that helps.

So stacker destroy doesn't delete/destroy any stacks by itself, you have to call it with --force to make it actually destroy a stack (otherwise it just lets you know what it plans to destroy).

Maybe if we have the termination protection configured via a config option, we can only allow destroying it if the config is later set to False.

I'll think about it some more - thanks again for the issue!