-
Notifications
You must be signed in to change notification settings - Fork 2.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
Allow to override the sts_endpoint when using sigv4auth #35297
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@Aneurysm9 @erichsueh3 please review? |
Component(s)
extension/sigv4auth
Is your feature request related to a problem? Please describe.
We have a use case where we need to override the sts_endpoint to use a private endpoint one. We couldn't find a way to do it with the current options available.
Describe the solution you'd like
The original issue that introduced the sigv4auth settings listed the
sts_endpoint
as an option, but it got dropped on the implementation part. Following the same approach would solve our issue.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: