[@aws-cdk/cloudwatch] Revert custom DashboardName generation once CloudFormation bug is fixed #213
Labels
@aws-cdk/aws-cloudwatch
Related to Amazon CloudWatch
Comments
piradeepk
pushed a commit
to piradeepk/aws-cdk
that referenced
this issue
Apr 25, 2019
There was a bug in CloudFormation which caused updates to `AWS::CloudWatch::Dashboard` to fail if `DashboardName` was not supplied. Now that the bug has been fixed we can revert the workaround in CDK which generates a name if the user doesn't supply one. Fixes aws#213.
SanderKnape
pushed a commit
to SanderKnape/aws-cdk
that referenced
this issue
May 14, 2019
There was a bug in CloudFormation which caused updates to `AWS::CloudWatch::Dashboard` to fail if `DashboardName` was not supplied. Now that the bug has been fixed we can revert the workaround in CDK which generates a name if the user doesn't supply one. Fixes aws#213.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a bug in CloudFormation which cases Updates to an
AWS::CloudWatch::Dashboardto fail ifDashboardNamewas not supplied.We now have a CDK-local workaround which will generate a name if the user didn't supply one.
Once the upstream bug is fixed, we should remove the workaround.
The text was updated successfully, but these errors were encountered: