Aws-cdk: Accentuation fail every time after cdk deploy with cdk diff

[webysther]

When 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: Bug Report

[RomainMuller]

Hey @webysther,

Would you be able to provide an example, so we can easily reproduce? If you can include the \u#### notation for the accented character as well, this will help make sure we are not falling victim to browsers or anything re-encoding it away from us...

[shivlaks]

marking this as a p2 for now, but will bump up if we have a min repro that affects a larger set of scenarios/use cases

[webysther]

@RomainMuller @shivlaks error sample repo, please follow the README.md instructions:

https://github.com/webysther/test-description-error-sample

[RomainMuller]

Turns out the problem is that CloudFormation itself mis-encodes your description and replaces both non-ASCII characters with ?s. It doesn't look like it's anything of CDK's doing.

The CDK is producing a JSON template including a correctly encoded UTF8 representation of your description. I am trying o engage with the CloudFormation service team to understand if this is a bug on their end.

[RomainMuller]

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]

Second internal reference: V137767984 (as we filed something that was closed as a duplicate).

This is not an action item for CDK, so I'm closing it.

[webysther]

Sorry @rix0rrr, can you be more clear?

[RomainMuller]

@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.