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
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
Thank you for this awesome solution but custom tags not working on any new resource created (tried with ec2) , pls help
did tried giving it in the below formats in the "AutoTag" stack set parameters
'{"key": "value"}'
"key": "value"
[{"key": "value"}]
but of no luck
The text was updated successfully, but these errors were encountered:
was trying to push a tag key along with its value and we've around 11
accounts with multiple regions being utilised but using the Stack Set (
https://github.com/GorillaStack/auto-tag/blob/master/STACKSET.md)
didn't work. no errors there but it just doesn't push the custom tag what
we give in the parameters section of the stack set where the auto deploy
option of stack works fine with the custom tags.
stack set uses autotag 0.5.0 version and the auto deploy script uses 0.5.5
Thank you,
Arunkumar
7892303637
On Tue, May 16, 2023 at 12:14 AM Ray ***@***.***> wrote:
The first one looks correct. I need to see exactly what you are doing and
what the error is. Did you try using one of the examples from the readme?
—
Reply to this email directly, view it on GitHub
<#113 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7YQ7VNHOYGBO2E53FJ5WWTXGJ2QHANCNFSM6AAAAAAX7GDCFU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for this awesome solution but custom tags not working on any new resource created (tried with ec2) , pls help
did tried giving it in the below formats in the "AutoTag" stack set parameters
'{"key": "value"}'
"key": "value"
[{"key": "value"}]
but of no luck
The text was updated successfully, but these errors were encountered: