Originally created by @twilkus on GitHub (May 19, 2025).
For example, when executing Batch Destroy Stack in a Procedure, target Stacks by tag. Maybe this is already possible using regex, but I didn't come across anything in the documentation about it.
It would be the same idea for whitelisting/blacklisting resources using tags for an Alerter.
Originally created by @twilkus on GitHub (May 19, 2025).
For example, when executing Batch Destroy Stack in a Procedure, target Stacks by tag. Maybe this is already possible using regex, but I didn't come across anything in the documentation about it.
It would be the same idea for whitelisting/blacklisting resources using tags for an Alerter.
Well, I was trying to do this without success, Thank god it is showing as an future enhancement, it will be very useful as I don't want automatically deploy or update containers that are tagged as critical when running my procedures, this is useful for lazy people like me that don't want to write every single stack that wants to be included in the stage.
@jeditec commented on GitHub (Dec 22, 2025):
Well, I was trying to do this without success, Thank god it is showing as an future enhancement, it will be very useful as I don't want automatically deploy or update containers that are tagged as critical when running my procedures, this is useful for lazy people like me that don't want to write every single stack that wants to be included in the stage.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @twilkus on GitHub (May 19, 2025).
For example, when executing Batch Destroy Stack in a Procedure, target Stacks by tag. Maybe this is already possible using regex, but I didn't come across anything in the documentation about it.
It would be the same idea for whitelisting/blacklisting resources using tags for an Alerter.
@jeditec commented on GitHub (Dec 22, 2025):
Well, I was trying to do this without success, Thank god it is showing as an future enhancement, it will be very useful as I don't want automatically deploy or update containers that are tagged as critical when running my procedures, this is useful for lazy people like me that don't want to write every single stack that wants to be included in the stage.