-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
support vault auth config for alicloud ca provider #16224
Merged
Merged
Conversation
This file contains 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
eikenb
added
type/enhancement
Proposed improvement or new feature
theme/connect
Anything related to Consul Connect, Service Mesh, Side Car Proxies
theme/consul-vault
Relating to Consul & Vault interactions
labels
Feb 9, 2023
github-actions
bot
added
the
pr/dependencies
PR specifically updates dependencies of project
label
Feb 9, 2023
eikenb
force-pushed
the
eikenb/alicloud-vault-provider-auth
branch
5 times, most recently
from
February 13, 2023 19:43
686f459
to
6fde5be
Compare
eikenb
force-pushed
the
eikenb/alicloud-vault-provider-auth
branch
2 times, most recently
from
March 1, 2023 01:05
e8fd763
to
fed6eab
Compare
cthain
reviewed
Mar 6, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. I left a couple of minor suggestions/comments.
cthain
approved these changes
Mar 6, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Add support for using existing vault auto-auth configurations as the provider configuration when using Vault's CA provider with AliCloud. AliCloud requires 2 extra fields to enable it to use STS (it's preferred auth setup). Our vault-plugin-auth-alicloud package contained a method to help generate them as they require you to make an http call to a faked endpoint proxy to get them (url and headers base64 encoded).
Seems like it'd be better to return them sooner rather than later.
Co-authored-by: Chris Thain <32781396+cthain@users.noreply.github.com>
Co-authored-by: Chris Thain <32781396+cthain@users.noreply.github.com>
eikenb
force-pushed
the
eikenb/alicloud-vault-provider-auth
branch
from
March 7, 2023 00:37
94fc053
to
fcd8cbb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
pr/dependencies
PR specifically updates dependencies of project
theme/connect
Anything related to Consul Connect, Service Mesh, Side Car Proxies
theme/consul-vault
Relating to Consul & Vault interactions
type/enhancement
Proposed improvement or new feature
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.
Add support for using existing vault auto-auth configurations as the provider configuration when using Vault's CA provider with AliCloud.
AliCloud requires 2 extra fields to enable it to use STS (it's preferred auth setup). Our vault-plugin-auth-alicloud package contained a method to help generate them as they require you to make an http call to a faked endpoint proxy to get them (url and headers base64 encoded).
PR Checklist
external facing docs updated(not doing on purpose)