Add metadata for AWS constructs are defined with a physical name

[eladb]

When an AWS construct is defined with an explicit physical name, we'd like to annotate the construct with metadata that contains that physical name, so that tools and aspects will be able to reason about it. We have a few examples throughout the library which add the aws:cdk:hasPhysicalName metadata entry for physical names, but we should normalize this though a common library.

[jungseoklee]

I am wondering how to normalize this.

I would like to solve a problem where we miss adding physical names to metadata. For example, DynamoDB and Kinesis L2 constructs add physical names to metadata, but SQS does not.

It is specific to service whether physical name is supported or not, so it seems tricky to handle it in a common library level.

[eladb]

There are two levels of "common" functionality:

1. Just a a common utility function that L2s can call in order to report that an explicit physical name was used.
2. Automatically-identify (e.g. through heuristics on the property names) that a physical name was used in L1.

I think all physical names are usually called Name or XxxName, so option #2 might actually be the pragmatic approach.

Perhaps this is also related somehow to #928 - maybe this utility will also supply some tools for L2s to make this easier to implement.

[jungseoklee]

Thanks for the answers.

I agree with an idea of #928, which helps to achieve the option 2 here.

[eladb]

We will reopen if this is relevant in the future.