Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[yoga] Set service_user_id from keystone relation #894

Conversation

rodrigogansobarbieri
Copy link
Contributor

This is necessary so we can avoid ambiguities (by using the id vs name) when we want to use the service user.

(cherry picked from commit f7e65d2) (cherry picked from commit 2320efd) (cherry picked from commit 7e325de) (cherry picked from commit 57331d4)

This is necessary so we can avoid ambiguities (by using the id vs
name) when we want to use the service user.

(cherry picked from commit f7e65d2)
(cherry picked from commit 2320efd)
(cherry picked from commit 7e325de)
(cherry picked from commit 57331d4)
@dosaboy dosaboy merged commit 4669229 into juju:stable/yoga Apr 19, 2024
3 checks passed
openstack-mirroring pushed a commit to openstack/charm-cinder that referenced this pull request Apr 19, 2024
admin_tenant_id is more explicit than admin_tenant_name
as project names might duplicate

This commit is related to code rdata.get -> _resolve.
Related commits are below but it is long.
So I changed _resolve to rdata.get here.

3faf38d3d8fa738d0582b4537e77eaef1d5c332a IndentityServiceContext app data fixes
4137a3d5d676ed6f332504b4edfcdf7f06c2f0bc
openstack: identity-service forwards compat (#730)

Charm-helpers-pr: juju/charm-helpers#894

Depends-on: I6807128492cb184de3ef5f454d0ea745246b242e

Closes-Bug: #2030755
Change-Id: Idbc2f3d12dcf325b4a53a3dda1ecfa75a199295a
(cherry picked from commit ff44269)
(cherry picked from commit 80115a2)
(cherry picked from commit e979c91)
(cherry picked from commit 73d596b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants