Explicitly Test Namespaces in AWS Provider

[skorfmann]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

cdktf & Language Versions

• 0.7

Affected Resource(s)

• AWS provider

The provider should be built and testes on a per namespace basis, since we had issues with single namespaces

[ansgarm]

@skorfmann How would that look like? Having synthesizable example code for every namespace the AWS provider has?

[skorfmann]

@skorfmann How would that look like? Having synthesizable example code for every namespace the AWS provider has?

I was thinking about some sort of auto generated testing. Not sure if that's feasible though

[DanielMSchmidt]

We figured that this is actually an upstream issue where a safe-guard was missing, tracking it under aws/jsii#3178

[ansgarm]

obsolete because this is both an upstream issue (improved there already) and because as of 0.13 we don't have specific namespaces for AWS anymore.

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.