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
Feature: all actions should have a parameter that allows for opting into / outof error === exit/skip #288
Comments
We have to get better at detecting errors and fail safely. We're working on this topic. This shouldn't be a thing the user should take care of |
Error handling is hard because our Atoms Definitely something we should improve in the short term |
Could we solve this by returning an Enum with wrapped values? enum ReturnValue {
SUCCESS,
ERROR(String)
} |
@airtonix We had a contributor call today about control flow, error handling, and output. We're going to add a manifest config option which will allow you to indicate a manifest can fail without stopping the apply. continue_on_error: true
actions:
- ... As well as this, we're going to rework the output for Comtrya to be more friendly and display better information to the user. Lastly, we're going to rework error handling all the way down Comtrya to propagate more useful error messages on failures. Thanks for your issues and continued patience. |
Description
Some actions are inconsistent with respects to how they handle errors.
Some will :
Perhaps we should think about a way to make this behaviour official and obvious to the user by:
on_error: die | skip_manifest | continue
die
I'm not sure what you consider the the correct wording and formatting, but essentially it should do two things:
Additional information
Add more context which didn't fit in the fields above.
The text was updated successfully, but these errors were encountered: