vSphere providers should be able to register custom model-config keys

[Tim McNamara]

The model-config command alerts users when they've defined a key/value that Juju doesn't know about. Because the client has access to the provider code, perhaps there should be a mechanism for the provider to be able to register keys that it knows about?

This is an acute problem with vsphere, as a few options are required:

  $ juju model-config datastore=H280-VIC847-0001
  WARNING key "datastore" is not defined in the current model configuration: possible misspelling

  $ juju model-config primary-network=VLAN_802
  WARNING key "primary-network" is not defined in the current model configuration: possible misspelling

[Heather Lanigan (hmlanigan)]

We have 4 sphere specific config keys defined:
https://github.com/juju/juju/blob/develop/provider/vsphere/config.go#L14

Including the 2 specifically listed.

Try:
juju show-cloud --include-config <name of defined vsphere cloud>

Though we've had reports that the config values are not included. That may be the problem.

[Heather Lanigan (hmlanigan)]

Looks like the vsphere provider is missing an implementation for:

func (p EnvironProvider) ConfigSchema() schema.Fields {

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

[Juan Pablo Noreña (jpablo-norena)]

Hi, this bug is affecting me in Juju 2.9.42

In a new model, it requires setting twice primary-network as config-model. The first time shows a warning:

WARNING key "primary-network" is not defined in the current model configuration: possible misspelling

The second time succeeded.

juju add-model test-model
juju model-config primary-network=<network-name>
WARNING key "primary-network" is not defined in the current model configuration: possible misspelling
juju model-config primary-network=<network-name>