You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to find the time one weekend to PR this myself, but adding it to GH issues for reference sake:
In an error scenario, the hogan CLI should exit with a non-zero status code to denote the error for consumers of the CLI.
For example if I am using hogan to generate configs as a part of my jenkins pipeline, I do not have an easy way to know whether or not the hogan config generation attempt failed or succeeded in my scripting.
Two scenarios I know of right now:
invalid hogan config dir specified
no matching environment in the configs dir... I do think this should produce an error
The text was updated successfully, but these errors were encountered:
I'd like to find the time one weekend to PR this myself, but adding it to GH issues for reference sake:
In an error scenario, the hogan CLI should exit with a non-zero status code to denote the error for consumers of the CLI.
For example if I am using hogan to generate configs as a part of my jenkins pipeline, I do not have an easy way to know whether or not the hogan config generation attempt failed or succeeded in my scripting.
Two scenarios I know of right now:
The text was updated successfully, but these errors were encountered: