-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Core: CfnCodeDeployBlueGreenHook TestTrafficRoute LogicalID cant be empty or undefined. #33020
Comments
if cloudformation is throwing this error, it seems CFN just doesn't allow it to be empty. Are you able to provide a tiny self-contained code snippet in this issue so I can rapidly reproduce it? |
Hi, apologies, setup for this issue can be quite involved. Here is an example of the CfnCodeDeployBlueGreenHook:
|
Describe the bug
The documentation for the CfnCodeDeployBlueGreenHook states that the test listener for the TrafficRoutingConfig object is optional. Furthermore the blue-green-hook-syntax example states the LogicalID for the TestTrafficRoute is not required.
However, the testTrafficRoute type does not allow undefined as a value, and when I provide an empty string I get the following error in my AWS CloudFormation stack:
Invalid CloudFormation template: Logical Resource ID cannot be empty
Regression Issue
Last Known Working CDK Version
No response
Expected Behavior
I can specify
undefined
or“”
for the TestTrafficRoute LogicalID, when no aws::ElasticLoadBalancingV2::Listener test listener Is required.Current Behavior
I get the following error in my AWS CloudFormation stack:
Invalid CloudFormation template: Logical Resource ID cannot be empty
Reproduction Steps
Recreate the CfnCodeDeployBlueGreenHook template example in cdk, and try to specify ”” for the testTrafficRoute LogicalID
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.164.1
Framework Version
No response
Node.js Version
v20.18.0
OS
MacOS
Language
TypeScript
Language Version
TypeScript (4.9.4)
Other information
No response
The text was updated successfully, but these errors were encountered: