(aws-ecr-assets): Custom ECR repository, custom name and/or tag #33228
Labels
@aws-cdk/aws-ecr-assets
Related to AWS CDK Docker Image Assets
effort/medium
Medium work item – several days of effort
feature-request
A feature should be added or improved.
p2
Describe the feature
Using CDK 2.177.0, it is not possible to declare custom ECR for images built to be used by ECS. Not only that, it's also impossible to tag those images meaningfully.
Allow user:
(if custom ECR is not possible, at least allow this as workaround)
This is follow up of #12597 and/or #25595 which have been closed without providing any working solution, and discussion #33157.
Use Case
Every image created for any project using same AWS account/region ends up in very same ECR which makes image management impossible. Reasoning why current CDK behavior is not optimal is well described in App Staging Synthesizer article (link below).
Tickets mentioned above failed to deliver any of this or replacement of CDK 1.0 behavior, because:
(failed to make it work with existing CDK project - can't actually provide better feedback)
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.177.0
Environment details (OS name and version, etc.)
linux, node:20-alpine
The text was updated successfully, but these errors were encountered: