Accentuation fail every time after cdk deploy with cdk diff
See original GitHub issueWhen I write some text in Portuguese that contains an accentuation the cdk diff breaks and shows differences every time.
Reproduction Steps
- Create a app
- Add description com accent: ‘maçã’
- Run
cdk diff; cdk deploy
- Run again
cdk diff
Environment
- CLI Version : 1…45.0 (build 0cfab15)
- Node.js Version: v12.18.0
- OS : Ubuntu 18.04 LTS
- Language (Version): Python 3.6.9
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
[aws-events] cdk diff shows difference, but cdk deploy tells no ...
I'm not sure whether this issue is involved with aws-events or cdk diff . Reproduction Steps. I have deployed this resource: import *...
Read more >Troubleshooting common AWS CDK issues
This topic describes how to troubleshoot the following issues with the AWS CDK. After updating the AWS CDK, the AWS CDK Toolkit (CLI)...
Read more >How to use `cdk diff` to programmatically check whether a ...
The --fail flag will cause cdk diff to exit with exit code 1 in case of a diff. Add conditional logic to handle...
Read more >CDK tips, part 6 – speeding up CDK application development
In part 6 of the 'CDK tips' series, we show how to accelerate deployments of code-only changes during development of CDK applications, ...
Read more >Lesson learned while I'm using CDK | by Jaewoo Ahn - Medium
Leverage cdk diff. It is common to see CloudFormation deployment works when you deploy the stack for the first time but it fails...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Alright I have filed an internal enquiry with CloudFormation to understand whether this is expected behavior / raise their attention to this problem.
Internal tracking number is
V215733201
.@rix0rrr is saying that the bug report I filed to CloudFormation was closed as duplicate of this other internal reference ID he’s reported against.
Since this is an issue in CloudFormation, there is nothing we need to do in the CDK directly, besides waiting for them to fix this.