Consider making ADMIN_DOMAIN and ADMIN_PROJECT configurable instead of having hard-coded constants
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Keystone Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Currently admin domain and project values are hard-coded in the keystone charm.
https:/
ADMIN_DOMAIN = 'admin_domain'
ADMIN_PROJECT = 'admin'
https:/
{% if api_version == 3 -%}
[resource]
admin_project_
admin_project_name = admin
They are used to set the following two keystone options:
https:/
admin_project_
admin_project_name = cfg.StrOpt(
It would be good to have those configurable as some 3-rd party integrated products have different expectations about these. Fixing 3-rd party products to support configurable values is the right approach but it is not always possible to do due to different non-technical reasons.
| Changed in charm-keystone: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Xav Paice (xavpaice) wrote | #2 |
| Dmitrii Shcherbakov (dmitriis) wrote | #3 |
This bug reads like a nice-to-have feature request.
The changes required to address this are non-trivial and expose a potentially dangerous configuration option.
The effort of implementation could be quite high, especially in ensuring cloud sanity in the case that these values are changed post-deployment on a running cloud with established workloads.
If this bug has more context to drive a higher level of importance than 'wishlist,' please clarify. Thank you.