This would add a method like .bucketName() or something to the builder that would use the bucketName provided. If the bucket doesn't exist, create it, otherwise use it, and put the data in a sub-bucket/folder, or use the full path provided.
Use Case
Generating many pipelines can run into S3 bucket limits. Being able to re-use an existing bucket would eliminate the bucket issue.
Proposed Solution
Add new method to blueprints.CodePipelineStack.builder() maybe called bucketName(), which takes in the bucket name/path, and KMS key ARN for encryption, then in code-pipeline.ts, where it creates the CodePipeline, pass in the value of artifactBucket to the parameters of the CodePipeline
Other Information
No response
Acknowledgements
[X] I may be able to implement this feature request
I just came across the same problem with too many pipelines. Until the feature arrives, i'll just delete the buckets (automatically) after i delete the pipeline.
Describe the feature
This would add a method like .bucketName() or something to the builder that would use the bucketName provided. If the bucket doesn't exist, create it, otherwise use it, and put the data in a sub-bucket/folder, or use the full path provided.
Use Case
Generating many pipelines can run into S3 bucket limits. Being able to re-use an existing bucket would eliminate the bucket issue.
Proposed Solution
Add new method to blueprints.CodePipelineStack.builder() maybe called bucketName(), which takes in the bucket name/path, and KMS key ARN for encryption, then in code-pipeline.ts, where it creates the CodePipeline, pass in the value of artifactBucket to the parameters of the CodePipeline
Other Information
No response
Acknowledgements
CDK version used
2.147.3
EKS Blueprints Version
1.15.1
Node.js Version
v20.17.0
Environment details (OS name and version, etc.)
ubuntu 24.04