-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Chalice generate-pipeline can create yaml incompatible with Cloudformation #450
Comments
I guess event name is generated from the view.view_name + HTTPMethod + digest. In this case generated one is generate_stuffpostc666 which is not acceptable as cloudformation accepts only alphnumeric. Possible fix is to remove non alphnumeric characters from view.view_name and then generated the event name. I have a fix in mind . Can I raise a pull request ? |
@corespace, In your test case, you may want to check for other non alphanumeric characters too. |
Yeah I wanted a better test, but it's not clear to me which characters are allowed and which are not. I assume alphanumeric means letters and number but I couldn't find any documentation confirming that. Hence why I haven't offered a fix either. |
Thanks for reporting this one. Marking it as a bug. |
@stealthycoin, Can I take this up ? I have found the fix. |
@achautha Sure feel free to open a pull request. |
… with Cloudformation
Fixed in #453 |
Hi folks,
I was working on a chalice app recently and decided to try out the chalice generate-pipeline feature. My app looked something like this:
I've left out some details, obviously, but this is enough to see the problem. When I ran generate pipeline and deployed that pipeline, it built out a CloudFormation yaml that included this:
Cool, right? Nope. Cloudformation barfed on this saying something to the effect "Event names must be alphanumeric" I don't have the exact error message anymore cause I went to retrieve it today and the ChangeSet is gone. Anyway, I created a test to reproduce the problem, but I'm not sure how you folks would want to rectify the problem. You can see it here: https://github.com/aws/chalice/compare/master...corespace:view_name?expand=1
The text was updated successfully, but these errors were encountered: