codepipeline: Add Branches and File Paths to CodePipeline pipeline GitPushFilter configuration

[einstein-aws]

Describe the feature

Currently, as it seems, only tag-based filters are available (or exposed) in CodePipeline pipeline GitPushFilter configuration via tagsExcludes and tagsIncludes parameters. However, both Branches and FilePaths options exist in CloudFormation spec https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codepipeline-pipeline-gitpushfilter.html Can you please add the two missing configuration parameters? Thanks!

Use Case

Branch-based pipeline trigger.

Proposed Solution

Add branchesExclude, branchesInclude, filePathsExclude and filePathsInclude parameters to match CloudFormation spec.

Other Information

No response

Acknowledgements

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

CDK version used

v2.128.0 (TypeScript)

Environment details (OS name and version, etc.)

MacOS Sonoma 14.3.1

[go-to-k]

I will take this issue.

[vumdao]

@go-to-k Can you please update for packages/aws-cdk-lib/pipelines/lib/codepipeline/codepipeline.ts either? Thanks.

[go-to-k]

@vumdao

The pipelines module already seems to be quite different in structure from aws-codepipeline. It might be better if you could create a separate issue with specific use cases.
In the meantime, we can pass existing pipelines to props, so that might help us meet the requirements even before we have to deal with that.

https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/pipelines/README.md#using-an-existing-aws-codepipeline

[pahud]

Awesome! Thank you for picking this up with a PR. @go-to-k

[jmihalich]

+1 for adding this to the cdk CodePipeline construct. I've been waiting for this.

Joe