-
Notifications
You must be signed in to change notification settings - Fork 4.1k
feat: allow overriding the filename of the processed file after substitution #29029
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
destinationKey
property to DeployTimeSubstitutedFile
constructdestinationKey
property to DeployTimeSubstitutedFile
construct
destinationKey
property to DeployTimeSubstitutedFile
constructdestinationKey
property to DeployTimeSubstitutedFile
construct
destinationKey
property to DeployTimeSubstitutedFile
constructdestinationKey
property to DeployTimeSubstitutedFile
construct
destinationKey
property to DeployTimeSubstitutedFile
constructdestinationKey
property to DeployTimeSubstitutedFile
destinationKey
property to DeployTimeSubstitutedFile
DeployTimeSubstitutedFile
DeployTimeSubstitutedFile
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
c96fa6f
to
ee5a554
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, a very minor comment. Also we generally name the PR like feat(module-name): summary
. So the title of this PR should be feat(s3-deployment): xxx
.
See link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
…construct. This allows users optionally indicate the resulting object key the processed file would be uploaded into.
b9044c2
to
ae877ce
Compare
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…itution (#29029) ### Issue # (if applicable) Closes #28450 ### Reason for this change Currently, the filename is automatically generated based on its fingerprint. There's no way to override the resulting filename. ### Description of changes Added an optional `destinationKey` parameter. If this is provided, the construct would use the `destinationKey` when uploading the resulting processed file to S3. If the `destinationKey` is not provided, the current approach would be the default. ### Description of how you validated changes Added a unit test to confirm that the correct filename is being used. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Issue # (if applicable)
Closes #28450
Reason for this change
Currently, the filename is automatically generated based on its fingerprint. There's no way to override the resulting filename.
Description of changes
Added an optional
destinationKey
parameter. If this is provided, the construct would use thedestinationKey
when uploading the resulting processed file to S3. If thedestinationKey
is not provided, the current approach would be the default.Description of how you validated changes
Added a unit test to confirm that the correct filename is being used.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license