Validate that charm configs are pointing to same releases
Bug #1871904 reported by
Drew Freiberger
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Lint |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
juju-lint should check for consistent
- openstack-origin
- source
- channel
settings across charms.
For instance, the channel on kubernetes-worker and kubernetes-master should match (e.g. "1.17/stable")
source across charms such as mysql, rabbitmq-server, ceph-mon, and ceph-osd should be compared. Potentially against openstack-origin for openstack charms.
Keystone openstack-origin should match all openstack-origins of other openstack charms, and series of applications should match (bionic/xenial/etc)
Revision history for this message
| James Hebden (ec0) wrote | #1 |
| Changed in juju-lint: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: bseng-198 |
Revision history for this message
| Gabriel Cocenza (gabrielcocenza) wrote | #2 |
To post a comment you must log in.
+1, great suggestion. I think implementing a "wildcard" charm name might make most sense.
Any settings specified under the wildcard could be checked only if the setting was present on the charm. We could also add a configuration operator of "same" or something that checked if the setting was consistent across the entire model.
This could of course be implemented today with the configuration checking logic, it would just lead to a lot of duplication, and the lint rules would need to be updated for each deployment, to match the desired OpenStack version.