Hi @eladb
Thank you for the prompt reply 😸

I'm a huge fan of the CDK and we have been using it since your first very early versions last year.
Keep up the good work 👍

As you mentioned in #5976, the intent of assets might be different from our use-case, which I will try to explain as best as possible.

When deploying new services to our AWS environments, we copy the application's build artifact into a folder within our AWS CDK TypeScript solution. This application's artifact contains a Dockerfile and is configured for the environment.

The workflow:

Get published artifacts from the application's build pipeline. No release pipeline or external ECR repository exists at this stage.
Copy artifact to an artifacts folder within the AWS CDK TypeScript solution.
The service is configured in TypeScript for the AWS CDK:
The application's Docker image is built as part of the CDK deployment to our account:
Once the AWS CDK deployment is complete, the service is running in a steady state. The initial seed is now complete.
We now use this repository created for the service, by the CDK and incorporate it into our release pipeline for the application. The service now gets deployed via the CI/CD pipeline and uses the repository created by the CDK.

Caveats and possible improvements on the process:

Ideally, we would like to be able to specify the name and tag of the created repository.
Rather than having cdk/< some lengthy name >< guid > we would prefer just < servicename >.
The container image after CDK deployment is marked with the latest tag, but the service task definition uses the SHA of the pushed image. Ideally, we would be able to specify the tag the task definition uses.
Using a shared repository, as introduced in the latest version of the CDK breaks this process, as the latest, dev, qa or build ID that might be used as tags by the release pipelines, could possibly not be unique for each service in the shared ECR assets repository.

Should you need more clarification on any of this, or more examples, I'd be more than happy to assist in any way possible. If it was possible for us to create, name and assign ECR repositories to ECS EC2 and ECS Fargate Services, and seed them with a locally built docker image, it would simplify and cleanup our workflow greatly! 🚀 🎉🎉

ECR assets: referencing outside of the CDK #5971

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions