This message was deleted.
# generals
sparse-intern-71089
04/07/2020, 6:56 PMThis message was deleted.
a
acoustic-florist-12628
04/07/2020, 7:22 PMWhile i believe this is doable with pulumi.all().apply(), for this specific use case the easiest solution is most likely with pulumi.interpolate. I'm not sure what language you're using, but in TypeScript it would look like this:
`const newarn = pulumi.interpolate`${lambda.arn}:${lambda.version}`;`
Note that after this operation, newarn is still of type Output<string>, it is not a string. It can be used directly as an input to other pulumi resources, but outside of .apply() it cannot be used in any functions expecting a string.
đź‘Ť 1
c
colossal-alarm-90650
04/07/2020, 7:29 PMHm. So what you are saying is that creation of the cloudfront consuming that value has to be done in an pulumi.all() in order for the value to be useful?
colossal-alarm-90650
04/07/2020, 7:35 PMNO. Sorry, I got a an error from AWS… as usual they are being difficult. Your solution worked perfectly, thanks a lot!!
đź‘Ť 1
colossal-alarm-90650
04/08/2020, 7:12 AM(Just fyi, it turns out that “lambda.version” does not evaluate to the “latest deployed version” as per the docs, but to the string “$LATEST”… which they naturally at the same time does NOT accept as input to a cloudfront edge lambda definition… so typically annoying. Pulumi unfortunately uses terraform as the interface rather than boto, so there’s no way of getting information about what the latest version is… I see a lot problems in that regard generally)
11 Views