feat: embed construct paths in CloudFormation metadata #1183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to allow tools that read a CloudFormation template created by
the CDK to be able to present the CDK path of resources in the template,
the CDK now embeds the full path as CloudFormation metadata "aws:cdk:path"
entry for each resource.
To disable this behavior use the switch
--no-path-metadata
or setpathMetadata
tofalse
incdk.json
or~/.cdk.json
.The toolkit can control this behavior by setting the
"aws:cdk:enable-path-metadata" context key. It sets it to
true
bydefault.
The default behavior of the Resource class is not to include
metadata. This is in order to maintain backwards compatibility
for tests.
cdk-integ
also disables this by default.Fixes #1182
Related #1121