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
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description:
In a recent version we were able to add tags in the toml file with spaces in the names -> these tags were added with no modification to resources.
In the current version it replaces spaces with an underscore:
samconfig.toml
I have tried with various formats of the tags arg with the same or worse results.
eg:
Note: spaces are explicitly allowed: https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html#:~:text=For%20information%20about%20what%20characters,and%20values%20are%20case%20sensitive.
This change is breaking out cost allocation tags, and breaking our CI scripts.
Steps to reproduce:
Using 1.132.0 Windows.
Observed result:
Replaces the tag with an underscore.
Cost Group -> Cost_Group
Expected result:
Creates the tag with the same name set in the samconfig.toml file.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: 1.132.0The text was updated successfully, but these errors were encountered: