-
Notifications
You must be signed in to change notification settings - Fork 421
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
Bug: copilot CLI fails if no default region found in profile #1115
Comments
Hi Guys, I'm new to that tool however it fails for me due to I checked out the repo https://github.com/aws-samples/aws-copilot-sample-service.git and run
I deliberately don't use the default region in my AWS config file and don't plan to start (as it is easy to execute to commend against the default region instead of intended one). @efekarakus how can I specify the region? Also this fails as well
UPDATE: |
Awesome glad you got it working @serverlesspolska ! |
I am trying to set up copilot init demo app using the interactive CLI but I am unable as the default AWS profile does not have region specified (an optional field) so the init command fails.
The missing feature in this case is a setting for --region parameter and optionally adding a prompt to the interactive init setup if it is not specified. Currently there is no such flag available, and surprised there isn't any planned in the roadmap.
Current workaround is to add the region manually into
~/.aws/config
if needed to deploy for any particular region which should not be needed as it forces user to change their default settings for profile. Alternately setting a new profile for this purpose for each required region is equally not a pleasant user experience.System tested on: Ubuntu 18.04 on WSL2
The text was updated successfully, but these errors were encountered: