Handle CDK resources with physical names

[corymhall]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

CDK and Pulumi handle resource naming differently. There are two naming scenarios for CDK:

1. Resources with an optional name property where CloudFormation will auto-name the resource.

• This maps perfectly to Pulumi's autoNaming feature.

2. Resource with a required name property. In most of these case CDK will use its own auto-naming strategy to populate the name property. During translation to Pulumi this leads to a hard coded name on the pulumi resource.

For the second scenario instead of populating the CDK hardcoded name, we should let Pulumi auto-name it. We still need to let users provide hardcoded names though.

One way we could accomplish this would be to inspect each construct and if it is a Resource then we can check to see if it has an unresolved physicalName defined. This means that it is generated by CDK (a value provided by the user would be a resolved value)

Affected area/feature