Add init and pre-init hook defaults as supported config options #542
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.
Since the
--init-hook
and--pre-init-hook
are the current method for resolving custom TLS certificates being needed by corporate proxies (see #493), being able to configure fixed hooks that don't need to be manually added on the command-line each time are useful.The variables already existed and could be overridden by the config files (which are just sourced into the scripts), but the
--pre-init-hook
was processed strangely and was appending the arguments needed when calling docker at argument parsing-time instead (see #497). The command-line options override the config file options already, so no changes were needed for that.Unrelated, but there was a typo in the
bashate
command in the CONTRIBUTING guide as well./closes #497