(pipelines): Add support for Amazon ECR source action

[alexpulver]

Add Amazon ECR source action to pipelines.CodePipelineSource class.

Use Case

Pipelines that trigger on push to Amazon ECR repository (e.g., base image update due to security CVE)

Proposed Solution

Add pipelines.CodePipelineSource.ecr(...) factory method.

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[npvisual]

@alexpulver : thanks for doing this 🙏. Been racking my brain trying to find a way around the limitation of CDK Pipeline sources for a little while. Glad I found your RFE !

Quick question : how would you trigger the CDK self-mutating pipeline from both a source code repo change and an ECR repo change ? Couldn't tell from the PR #16385

Since the pipeline needs to watch for changes in its own code, the primary source has to be the source code repo, I'd guess. But then how would you add the ECR repo source ? The current parameters in ShellStep define additional_inputs but that just seems to fit another source code repo.

[stockf]

additional_inputs works. The pipeline ist then also triggered when a new image is pushed.

[npvisual]

@stockf : thanks for the response. Agreed. I tested this with a "local" implementation of the changes provided in the PR and it works like a charm. Here's the snipper in Python :

        build_step = pipelines.ShellStep(
            "Synth",
            input=code_source,
            additional_inputs={
                "ecr_artifact": ecr_source,
            },
           ...

The source stage of the pipeline will have both actions defined in parallel and the pipeline will get triggered for either an update to the source code or the ECR repo.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.