This message was deleted.

Here is an issue tracking making those types of functions easier to use with `Input<T>`: https://github.com/pulumi/pulumi/issues/5758 In the meantime, yes, you will need to

apply

and/or

all

to project your async values into the function.

For the policy document case, there is a Pulumi-native alternative in the aws.iam.PolicyDocuemnt class. Most resources that have a policy property have type

pulumi.Input<string> | aws.iam.PolicyDocument

.

I don’t think that is present in all SDKs, unless it’s new. I may be mistaken though. C# particularly obviously can’t do the built in type union but they might be using their Union generic. But if you have an Output<PolicyDocument> because you needed output to build the document than you’d still use the Input<string> I believe

Awesome, thanks