-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
approle: Include role_name in alias metadata #9529
Conversation
This change allows people who are using templated policies to use the role_name in their templates through {{ identity.entity.aliases.approle.metadata.role_name }}.
Test failure seems like a flake, but it looks like Circle doesn’t let external folks re-run tests :( |
@calvn As this metadata is stable (i.e. not a volatile instance_id or the like) I think it would be OK to store by default. WDYT? |
@kalafut Yeah that's my understanding here too :) - and seems to hold up in my test environment with this patch deployed |
Merging this one. The race failure does not seem to be related. |
This change allows people who are using templated policies to use the role_name in their templates through {{ identity.entity.aliases.approle.metadata.role_name }}. Co-authored-by: Calvin Leung Huang <[email protected]>
This change allows people who are using templated policies to use the role_name in their templates through {{ identity.entity.aliases.approle.metadata.role_name }}. Co-authored-by: Calvin Leung Huang <[email protected]> Co-authored-by: Danielle <[email protected]>
@calvn thanks! 🎉 ✨ |
Just a small contribution for everyone who would have issues get their acls to work with the above feature. It is |
This change allows people who are using templated policies to use the role's name in their templates through
{{ identity.entity.aliases.approle.metadata.role_name }}
.I'm not sure if there is a better place to implement this, but it seems like the most reliable bet to ensure that it gets populated on future logins?
Closes #8128.