-
Notifications
You must be signed in to change notification settings - Fork 80
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
region
parameter not correctly override ${AWS_DEFAULT_REGION} env
#220
Comments
I think this new version should solve your problem 5.2.1 |
Thanks for the quick respond, seems to be able to point out region from parameters. +@
|
The initial design of the orb was to use the environment variables for the region. For the update_service command there was a recent addition of the parameter to solve some specific situation and that's why it't the only having it. |
Thanks for working on this issue ✨ Support are receiving request from user that it would be beneficial to be able to pass on pipeline parameters like the other command. Will the team able to also apply it for
|
Hi @nanophate I'm working on an update for that. The idea is to standardize it and let all the commands and jobs using the region parameter. |
Version 6.0.0 now has a region parameter for all the jobs and commands. I'm going to close this issue. |
Orb version:
5.x
What happened:
During the running
deploy_service_update
job, it's generate errorInvalid endpoint: https://ecs..amazonaws.com
It's seems to error related missing
region
parameter, but it's correctly setup already.However, it's resolved when setting ${AWS_DEFAULT_REGION} which should be an optional.
Seems to during the steps, it directly refer to ${AWS_DEFAULT_REGION} env not parameter.
Expected behavior:
Make it
region
parameter override ${AWS_DEFAULT_REGION} env, and correct command refer to parameter.Additional Information:
Taking look
deploy_service_update
job on orb source 5.x, below steps were included.And it's not using registered parameter but only take it directly from ${AWS_DEFAULT_REGION}.
Same steps on version 4.1, there was no region flag. So I assuming it's only effected on 5.x.
The text was updated successfully, but these errors were encountered: