feat: add v3 Keystone trust auth support#105
Merged
Merged
Conversation
wallyworld
approved these changes
Apr 30, 2026
hmlanigan
approved these changes
Apr 30, 2026
hmlanigan
left a comment
Member
There was a problem hiding this comment.
It may not be possible in this PR, but moving to go 1.26 would be good.
b56e22b to
71d6a86
Compare
71d6a86 to
6f27cc0
Compare
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
3 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.
This adds support for Keystone Trusts.
The change is quite simple - a single, optional extra field in the
Credentialsstruct for supplying a trust ID.