You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins 30204ecded command/cliconfig: Allow development overrides for providers ... For normal provider installation we want to associate each provider with a selected version number and find a suitable package for that version that conforms to the official hashes for that release. Those requirements are very onerous for a provider developer currently testing a not-yet-released build, though. To allow for that case this new CLI configuration feature allows overriding specific providers to refer to give local filesystem directories. Any provider overridden in this way is not subject to the usual restrictions about selected versions or checksum conformance, and activating an override won't cause any changes to the selections recorded in the lock file because it's intended to be a temporary setting for one developer only. This is, in a sense, a spiritual successor of an old capability we had to override specific plugins in the CLI configuration file. There were some vestiges of that left in the main package and CLI config package but nothing has actually been honoring them for several versions now and so this commit removes them to avoid confusion with the new mechanism.		5 years ago
..
config	command/cliconfig: Factor out CLI config handling	7 years ago
config-env	command/cliconfig: Factor out CLI config handling	7 years ago
credentials	command/cliconfig: Factor out CLI config handling	7 years ago
hosts	command/cliconfig: Factor out CLI config handling	7 years ago
provider-installation	command/cliconfig: Allow development overrides for providers	5 years ago
provider-installation-errors	command/cliconfig: Decode provider_installation blocks	6 years ago
provider-installation.json	command/cliconfig: Allow development overrides for providers	5 years ago