You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If two top-level resources (resources defined directly under a stack) have logical IDs that only differ by non alpha-numeric characters, they will get the same logical ID and will conflict.
Sadly, we can't fix this bug without a breaking change in 1.x, so we should consider fixing this in v2.0.
If two top-level resources (resources defined directly under a stack) have logical IDs that only differ by non alpha-numeric characters, they will get the same logical ID and will conflict.
Sadly, we can't fix this bug without a breaking change in 1.x, so we should consider fixing this in v2.0.
Reproduction Steps
In this case, both
r1
andr2
will get the logical IDab
because we filter non-alphanumeric characters from the logical ID for top-level resources.Other
The code is here:
aws-cdk/packages/@aws-cdk/core/lib/private/uniqueid.ts
Line 49 in 031932d
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: