-
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
(core): ExportValue does not automatically detect attribute name #12918
Comments
Hi! Without having seen more code (such as the definition of ... can I guess that If not, please supply a minimal working example. |
Sadly no, here is an actual example I used, in a similar way:
Difference here is that I use the ExportValue directly on the stack, in my original problem i used it on another stack that referenced this |
Most L2 resources employ the "PhysicalName" protocol, which checks usage of resource names across environment borders, and can automatically turn auto-named resources into physically-named resources if the situation calls for it. Unfortunately, this wrapped token is a generic IResolvable, not a Reference, and so did not work with the `exportValue()` automatic reference detection. Make the token returned by `getResourceNameAttribute()` etc. a `Reference` that mimics the underlying `Reference` to make this work out. Fixes #13002, fixes #12918.
Most L2 resources employ the "PhysicalName" protocol, which checks usage of resource names across environment borders, and can automatically turn auto-named resources into physically-named resources if the situation calls for it. Unfortunately, this wrapped token is a generic IResolvable, not a Reference, and so did not work with the `exportValue()` automatic reference detection. Make the token returned by `getResourceNameAttribute()` etc. a `Reference` that mimics the underlying `Reference` to make this work out. Fixes #13002, fixes #12918. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Most L2 resources employ the "PhysicalName" protocol, which checks usage of resource names across environment borders, and can automatically turn auto-named resources into physically-named resources if the situation calls for it. Unfortunately, this wrapped token is a generic IResolvable, not a Reference, and so did not work with the `exportValue()` automatic reference detection. Make the token returned by `getResourceNameAttribute()` etc. a `Reference` that mimics the underlying `Reference` to make this work out. Fixes aws#13002, fixes aws#12918. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Most L2 resources employ the "PhysicalName" protocol, which checks usage of resource names across environment borders, and can automatically turn auto-named resources into physically-named resources if the situation calls for it. Unfortunately, this wrapped token is a generic IResolvable, not a Reference, and so did not work with the `exportValue()` automatic reference detection. Make the token returned by `getResourceNameAttribute()` etc. a `Reference` that mimics the underlying `Reference` to make this work out. Fixes #13002, fixes #12918. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Not possible to add
ExportValue
without specified name, even if the specific error says it should work this wayReproduction Steps
Have two stacks, one with a backup bucket that i used the name from in another stack.
Removed the usage and added the
ExportValue
to avoid getting the cross stack errorthis.ExportValue(destinationStack.BackupBucket.BucketName);
Reproduceable steps using the original
BucketStack
directly:What did you expect to happen?
To create a
ExportValue
without having to add a nameWhat actually happened?
Unhandled exception. Amazon.JSII.Runtime.JsiiException: exportValue: either supply 'name' or make sure to export a resource attribute (like 'bucket.bucketName')
Environment
Other
Workaround is the add a name to the
ExportValueOptions
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: