These were previously settable only via environment variables. These are
now handled as part of CLI Configuration and so also settable in a new
"registry_protocols" block in a CLI configuration file, with the
environment variables now treated as if they are an additional virtual
configuration file containing the corresponding settings.
This handles our settings in our modern style where package cliconfig is
responsible for deciding the configuration and then package main reacts
to that configuration without being aware of how it is decided.
Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
* Initial renaming, rewriting and cleaning up wave for the CLI docs.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* More renaming.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* More renaming.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* More renaming.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Remove tutorial references.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
* Post-review fixes.
Signed-off-by: Jakub Martin <kubam@spacelift.io>
---------
Signed-off-by: Jakub Martin <kubam@spacelift.io>
This is an alternative way to set the CLI configuration setting
plugin_cache_may_break_dependency_lock_file to activate the transitional
compatibility behavior that prefers to break the dependency lock file if
that would create an additional opportunity to use the plugin cache.
