thar-be-settings: log a render error when running in --all mode #427
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.
When running in
--all
mode, thar-be-settings (intentionally) does not failwhen a template fails to render. This commit logs a message
with the appropriate details in the event of a failure.
Issue #, if available:
Fixes #412
Description of changes:
match
statement to catch and log theErr()
case.Testing done:
Run
thar-be-settings
with a setting passed on the command line:Run
thar-be-settings --all
on a system where a few kubernetes settings don't exist:By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.