-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Fix: Return proper client error for invalid YAML template structure #13300
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
Conversation
|
Converted to draft as I misunderstood the issue, will work on it later on. |
|
This is awesome, thank you for at least starting this change! I look forward to seeing where it goes. Do you want my initial comments now or should I wait until you are happy with the PR? |
let's wait, I will remove draft status when ready. |
|
Ok I think it's ready for review now @simonrw. |
simonrw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank you for your contribution. There are still some rough edges around the new engine and validation, so thank you for catching this one!
Motivation
Fixes #12309
Add snapshot testing for CloudFormation stack creation with EC2 templates that include CloudFormation Init functionality.
Correctly raise an
ClientErrorwhen invalidyamlfile is provided.Changes
test_create_stack_from_templateyamlparser for cloudeformation engine.