Comment 1 for bug 1814786
Revision history for this message
| Ian Booth (wallyworld) wrote Re: Regression: juju bootstrap does not error on unknown or incorrect config values | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Did Juju ever error as opposed to warn about config attributes that didn't match the schema? For a long time, Juju had no way of allowing model config that was provider specific, so it had to allow unknown attributes to be set - the provider would use them but the attribute was unrecognised by Juju's config schema. eg AWS clouds can have a vpc-id, Openstack can have use-floating-ip etc. So Juju just used to warn about such values. And I suspect that behaviour still exists today. Or are you saying for controller config, we used to be more strict and genuinely did error?