-
Notifications
You must be signed in to change notification settings - Fork 68
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
Error when creating aliases with "-" in the name #68
Comments
I will use normalized alias names internally. The dashes have to be replaced by |
Any update on when this might be added in? Our team would love to tie this into our automated deployment (we tag our assets based on JIRA story key, which contains dashes!). Love this plugin so far. |
@mbruning24 Sorry, that there wasn't any progress on that yet. I was quite busy with Adding this should not be much efforts if it is only done for the rule name, and only if it contains disallowed characters (which is a fixed set) to stay backwards compatible. |
Released with 1.5.1 |
FYI, this issue is mentioned as "Support _ - + in alias names #68" in the README, but only hyphens work. If I try to use a + or _ I get |
Any update on the above mentioned query. |
@chosme could you provide |
I've tried to deploy a new alias called "my-test" using
sls deploy --alias my-test
. Unfortunately this fails with an exception:The alias stack is still created and not cleaned up properly. I suggest to simply use camel casing when appending the alias name to CloudFormation resources. That would fix this while still allowing non alphanumeric characters in the alias name itself.
The text was updated successfully, but these errors were encountered: