-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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.
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
Allow wildcards in target #2444
Comments
The ability the address an entire resource would be greatly appreciated, for example: |
+1 to this request. Alternatively, an exclude tag for destruction would also be useful. Our use case is wanting to scorch the earth of all our infrastructure except for certain elements such as ELB's to avoid DNS delays. |
Very useful feature. |
+1 |
It would be nice to add wild cards like these too |
+1 |
Hey all – thanks for the suggestion; I'm going to close this a duplicate of #2182 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
It would be nice to be able to use wildcards in the target command for generating plans and applying changes.
My use case is that I want to roll out changes to my infrastructure in stages based on a naming convention.
For example:
The current output of this is:
I do realise that this is possible using sub-directories and generating plans for each, but this solution proves more flexible.
Thanks!
The text was updated successfully, but these errors were encountered: