Skip to content
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

ECR Region configuration variable #90

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

brianwallace
Copy link

This PR adds a new configuration variable called ecr-region. It allows you to run vili in one region, but configure vili to connect to an ECR repo in a different AWS region.

app/vili.go Outdated
@@ -159,7 +159,7 @@ func New() *App {
registryID = &ecrAccountID
}
err := repository.InitECR(&repository.ECRConfig{
Region: config.GetString(config.AWSRegion),
Region: config.GetString(config.ECRRegion),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this fall back to AWSRegion if blank?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point!

I usually think that explicit configuration is best, so I made the ecr-region a required configuration variable. Let me know what you think..... if this doesn't make sense, happy to change this to fall back to using the aws-region instead.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After an end of the day conversation with @BrianBland yesterday, we decided to change the logic to default to using the aws-region variable if ecr-region is not set.

I've added logic to make this so.

Default to using the aws-region variable of the ecr-region is not explicityly set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants