You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
consider grouping all the "command hooks" under hooks or command_hooks instead of directly under the template name.
an extension would be to support all/other commands other than apply and delete.
consider renaming the actions directory to hooks or command_hooks.
depending on use case, it may be preferable to always execute the post_<command> hooks regardless if the exit status of the pre_<command> hooks. In this case, a "command status" parameter is passed to the post hooks. For example, the post hooks could be used for some cleanup of the pre hooks that you always want to run.
should post command hooks be executed if the command fails?
To be clear, I'm not suggesting increasing the scope of this proposal, just some things to think about so it can be extended in the future :)
It would be great if stacks could be setup so certain actions (or hooks) could run before and after applying and deleting them.
In my head, indicating the actions would be done in the
stack_master.yml
itself. Something like:pre_apply
post_apply
pre_delete
post_delete
pre_delete
.If the script returns zero, then
stack_master
would continue execution. Any non-zero return code would interrupt the execution.Actions would be located under an
actions
directory at the same level asparameters
,templates
, etc.The text was updated successfully, but these errors were encountered: