aws / aws/aws-cdk

[aws-cdk-lib/pipelines] Support file path filters in trigger

Open
#35,379 4 comments 2 reactions 0 assignees View on GitHub
@aws-cdk/triggers effort/medium feature-request p2
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

### Describe the feature

The L2 construct `aws-cdk-lib/aws-codepipeline` support adding trigger and support file paths filter, but the L3 construct `aws-cdk-lib/pipelines` does not support it.

Image

I wonder if we have a plan to add this support, and also want to know if there is a walkaround now to add path filter in L3 without changing it back to L2.

### Use Case

I need to use file path filter for my monorepo/microfrontend project, so pipeline will be deployed only when a change happen in a particular folder.

### Proposed Solution

Add a file path filter option in pipeline props.

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS CDK Library version (aws-cdk-lib)

2.213.0

### AWS CDK CLI version

2.1027.0

### Environment details (OS name and version, etc.)

macos

Contributor guide

Open the contributing guide

Research direction

Start at the TypeScript entry points for aws-cdk-lib/pipelines and compare their trigger handling with the file-path filter support in aws-cdk-lib/aws-codepipeline. Trace how pipeline props reach the generated trigger; done means L3 pipeline props accept file path filters and deployments run only for changes in the selected paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
ci-cd, cloud, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.