-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add metadata for AWS constructs are defined with a physical name #92
Comments
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. |
There are two levels of "common" functionality:
I think all physical names are usually called Perhaps this is also related somehow to #928 - maybe this utility will also supply some tools for L2s to make this easier to implement. |
Thanks for the answers. I agree with an idea of #928, which helps to achieve the option 2 here. |
We will reopen if this is relevant in the future. |
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.The text was updated successfully, but these errors were encountered: