-
Notifications
You must be signed in to change notification settings - Fork 13
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested variable resolution #506
Comments
As an alternative, would (This is a straw proposal, but I think this would be a lower lift than changing the expression syntax similar to how you've described.) # all other keys identical to example
resources:
# Create an AWS resource (S3 Bucket)
my-bucket:
type: aws:s3:Bucket
properties:
tags:
project:
fn::select:
- ${selector}
- ${projectDescription} |
variables:
projectDescription:
regionA:
projectA: "This is region A, project A"
projectB: "This is region A, project B"
regionB:
projectA: "This is region B, project A"
projectB: "This is region B, project B"
config:
regionSelector: "regionA"
projectSelector: "projectA"
|
Why not |
yep, that works too. |
@Frassle changing the substitution parsing requires more significant changes, changing or adding a built-in is lower lift. However I'm wondering if It looks like |
Hello!
Issue details
Currently, pulumi YAML is unable to resolve nested variables such as this example. The important line here being
project: ${projectDescription.${selector}}
where the project description could be fetThe
pulumi pre --diff
showsI've also tried using
project: ${projectDescription}.${selector}
but this returns:Affected area/feature
The text was updated successfully, but these errors were encountered: