-
Notifications
You must be signed in to change notification settings - Fork 440
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
fix: Use property access when refrencing numeric and map accessors #2801
Conversation
ed015ba
to
bf18865
Compare
bf18865
to
c1a88d5
Compare
2e856a5
to
f604898
Compare
e8b2c1d
to
d003dfd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Related issue
Fixes https://github.com/orgs/hashicorp/projects/207/views/12?pane=issue&itemId=25543682
Description
Using String templates instead of propertyAccess causes problems with nesting template strings (which would need more context to solve properly), and also when used within CDKTF functions. This PR moves most template string usage that required use of FQN over to using the CDKTF propertyAccess function.
Checklist