feat(openstack): support Keystone v3 domains in OpenStack provider#31
Merged
Merged
Conversation
Read optional `user_domain` and `project_domain` from the
[PROV_OPENSTACK] section and forward them to novaclient's
Client() as `user_domain_name` / `project_domain_name`.
Both default to 'Default' when not set, keeping the existing
behaviour for legacy Keystone v2.0 deployments. This unlocks
authentication against OpenStack 2025.2 (Keystone v3 only),
which otherwise returns:
400 Expecting to find domain in user.
Tested against an OpenStack 2025.2 Kolla deployment (Terralta
POC), with the project living in a non-Default domain.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Read optional
user_domainandproject_domainfrom the [PROV_OPENSTACK] section and forward them to novaclient's Client() asuser_domain_name/project_domain_name.Both default to 'Default' when not set, keeping the existing behaviour for legacy Keystone v2.0 deployments. This unlocks authentication against OpenStack 2025.2 (Keystone v3 only), which otherwise returns: