-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
CFn: improve error messages #11591
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
CFn: improve error messages #11591
Conversation
13f53f1
to
bfb4a18
Compare
The CI is green apart from one failing test with the arm tests: |
bfb4a18
to
0cff704
Compare
0cff704
to
5109aa9
Compare
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.
LGTM! Nice addition to improve clarity and allow for more insight into root causes. In terms of the tests, I think it might be good to separate these kind of tests a bit more (e.g. a separate class) but that's more of an optional nit and up for discussion at a later point.
Motivation
When using our CloudFormation implementation, we often don't change errors when they are raised. This usually means the user is faced with horrible Python tracebacks that require our input to resolve.
A much better story is to parse and validate the template by converting the template into a meaningful graph of resources, with parameters, conditions and mappings resolved at template parse time, however we are not quite at that stage yet. The CFn implementation in LocalStack currently works, but is not pretty, and would take some effort to re-write at the moment, and at this stage it is not worth it.
The next best thing is to loose focus on parity with AWS and do what we can by improving error messages on obvious conditions. This PR tackles some of these things.
Changes
TODO
More improvements...