-
Notifications
You must be signed in to change notification settings - Fork 17
feat: Add support for AWS_STS_REGIONAL_ENDPOINTS #230
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
Conversation
Add the environment variable to the coder service as well
I have tested this on my local deployment the following :
|
@ericpaulsen do you want me to squash some commits ? |
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.
this looks good to me. however, prior to merging, i'd like for our engineers to provide their input, in case i'm missing anything.
we have squash & merge on by default. thank you for contributing!
Sorry about this taking so long, I'm going try to make a separate PR today that adds support for arbitrary env variables on coderd and I'll ping you for review :) |
Hello, if you are busy at the moment I do not mind implementing this feature. How I see it would require to modify this MR to allow for |
Thanks for this PR, I've made the env vars change in #236 which will land in 1.29.1 and 1.30.0. |
AWS_STS_REGIONAL_ENDPOINTS
value isregional
values.yaml
:awsStsRegionalEndpoints.enable
(false by default) which activates the environment variableAWS_STS_REGIONAL_ENDPOINTS
I have not yet tested this on a coder deployment, I will remove the WIP once I can confirm it works as intended.