(assets): force re-generation of assets via the CLI (Re-open issue #12800)

[jk2l]

Describe the feature

Currently CDK ignore asset upload if asset already exist, the CDK will ignore publish it. However in a scenario the asset is corrupted due to bug, there is no way to fix it beside manually hunt down individual asset in S3 bucket and delete them.

Use Case

If the asset is corrupted/broken, admin should be able to force re-publish the the assets

Proposed Solution

add a new flag --force-publish, update the code under https://github.com/aws/aws-cdk/blob/main/packages/cdk-assets/lib/private/handlers/files.ts and update check related to objectExists() against the asset

Other Information

Historical issues that cause corrupted asset:

• lambda: corrupt zip archive asset produced when using node v15.6 #12536
• (cdk-assets): Parallel zipping same asset with cdk deploy --concurrency 2 has chance to create and permanently upload corrupted asset to S3 #23290
• core: Asset bundling ignored when deploy with --exclusive flag with nested stack #30967

Historical issues that require re-publish asset:

• core: Differing CDK assets not deploy if already deployed. #30962

Proposed tickets that is now closed:

• (assets): force re-generation of assets via the CLI #12800
• (assets): Request to add --force publish option #12440

Acknowledgements

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

CDK version used

1.150.0

Environment details (OS name and version, etc.)

Ubuntu 22.04