aws-cdk icon indicating copy to clipboard operation
aws-cdk copied to clipboard

Issue deploying CDK without the custom resource updating.

Open jacido opened this issue 1 year ago • 3 comments

Describe the bug

A CDK custom resource is unexpectedly updating causing a dependency issue. They have not made any changes to the custom resource change set. and they do not want it to change.

Error: Received response status [FAILED] from custom resource. Message returned: Package @aws-sdk/client-kafka does not exist. (RequestId: XXXXXXX-39c5-XXXe-8160-XXX1821XXXXX)

Expected Behavior

Not expected behavior.

Current Behavior

The stack failed to deploy due to dependency issues. The this stack has an EXPORT that is being used many consuming stacks it's the custom resource named ClusterBootstrapBrokersBootstrapBrokerStringXXXXXXXXXXXX that is being updated causing the dependency issue. They have not made any changes to the custom resource change set. and they do not want it to change.

Reproduction Steps

TBD

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.118

Framework Version

No response

Node.js Version

nodejs18.x

OS

N/A

Language

Python

Language Version

Python

Other information

Attached screenshot of cdk diff results comparing code to being deployed and the current production state. They are using CDK library 2.118

Screenshot 2024-05-06 at 3 46 41 PM

jacido avatar May 07 '24 17:05 jacido

Same issue with you but in other package:




❌  bridge-api-v2-dev failed: Error: The stack named XXXXXXXX failed to deploy: UPDATE_ROLLBACK_FAILED (The following resource(s) failed to update: [XXXXXXX]. ): Received response status [FAILED] from custom resource. Message returned: Package @aws-sdk/client-ssm does not exist. (RequestId:XXXXXXXXXXX)

coolbitxColma avatar May 08 '24 01:05 coolbitxColma

probably related to https://github.com/aws/aws-cdk/issues/30067

pahud avatar May 08 '24 01:05 pahud

Today before another round of CDK deployment, we did cdk diff on the stack, it shows no changes comparing the production environment. However, the actual deployment dies on the custom resource.

aalanzhao avatar May 08 '24 15:05 aalanzhao

Is there any progress on this issue? This is also affecting our CFN stacks with custom resources

emmanuelnk avatar Jun 05 '24 19:06 emmanuelnk