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
I'm trying to create an EBS volume with a tag "a.b" = "c"
However, it looks like the value is not recognized when the key has a dot. A tag is created with the correct name but an empty value. I've tried escaping the dot but can't find the magic syntax.
The text was updated successfully, but these errors were encountered:
justinsb
changed the title
Parsing problem prevents creation of AWS tags contains "."
Parsing problem prevents creation of AWS tags containing "."
Jun 8, 2016
justinsb
changed the title
Parsing problem prevents creation of AWS tags containing "."
Cannot create AWS tags containing "."
Jun 8, 2016
justinsb
changed the title
Cannot create AWS tags containing "."
Cannot create EC2 tags containing "."
Jun 8, 2016
Thanks for the report, I'm closing as a duplicate of #2143
I think this may actually be fixed in master (& 0.7.0rc), but we'll need to verify before closing #2143
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.
ghost
locked and limited conversation to collaborators
Apr 25, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to create an EBS volume with a tag "a.b" = "c"
However, it looks like the value is not recognized when the key has a dot. A tag is created with the correct name but an empty value. I've tried escaping the dot but can't find the magic syntax.
Here's a short repro:
After
terraform apply
,aws ec2 describe-volumes
showsThe value should be
c
, but is empty.Changing the key to
ab
(no dot) works correctly.The text was updated successfully, but these errors were encountered: