-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix: ECR pull through cache pattern #1980
Conversation
@@ -1,3 +1,9 @@ | |||
locals { | |||
ecr_account_id = var.ecr_account_id != "" ? var.ecr_account_id : data.aws_caller_identity.current.account_id |
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.
lets remove account ID and region entirely - we can get this data from the provider/data sources
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.
I kept those as different from the main region/account to illustrate that's possible to use an ECR on a different region/account, not required to be the same as the cluster deployment.
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.
looks great, thank you!
Description
Motivation and Context
Fit pattern to EKS Blueprints standards.
How was this change tested?
pre-commit run -a
with this PRAdditional Notes