Better exceptions handling during pipeline deployment #48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #47.
I've added the bare minimum to handle any unhandled exceptions during pipeline deployment (now it returns a HTTP 500 with error details).
I've also added tests for pipeline registry, which was uncovered.
Of course, this is the bare minimum to avoid to throw and broke during pipeline deployment. I plan to add further minor improvements such as: