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
Would it be possible to add an option so that, in non-interactive mode when a parameter is missing, an exception is thrown rather than the default copied from the .dist file?
Use-case: The parameter handler is great for our developers when they are working. But our deployments are automated. Usually the defaults given in .dist are not suitable for CI, QA or production environments. I want our build process to fail when keys are missing from our parameters file, and not copy the defaults.
The text was updated successfully, but these errors were encountered:
silvant
pushed a commit
to silvant/ParameterHandler
that referenced
this issue
Jan 18, 2017
Would it be possible to add an option so that, in non-interactive mode when a parameter is missing, an exception is thrown rather than the default copied from the .dist file?
Use-case: The parameter handler is great for our developers when they are working. But our deployments are automated. Usually the defaults given in .dist are not suitable for CI, QA or production environments. I want our build process to fail when keys are missing from our parameters file, and not copy the defaults.
The text was updated successfully, but these errors were encountered: