https://pulumi.com
Join Slack
This message was deleted.
# dotnet
s
This message was deleted.
Untitled
t
Yes, you should be able to do that..
You can either derive from the 
Stack
class or pass a function to 
RunAsync
, both will work including outputs.
I don’t think this is related to the error from James though?
I also responded in the thread above
b
Is it correct to say that if I wanted to use some value from a StackReference, like creating a LoadBalancer, I would need to create the LoadBalancer withing the Apply? Output.Create won't away right?
t
You could assign values from a stack reference to the Load Balancer properties.
Creating resources inside Apply is not recommended.
b
So if a value in a stack reference is needed and GetOutput is being used, how do you know if that task will complete before the creation of the resource that uses the value?
async await make async usable in a sync fasion, i'm trying to understand how [Output] and Apply does that.
t
Outputs take care of ordering for you, that’s the beauty. Once you have an output, you can freely use it everywhere.
Outputs are based on Tasks internally and we do completion sources etc behind the scenes.
b
So outputs, regardless of how many, are resolved before resource creation?
t
Yes. You can define a resource using unresolved outputs (as you do almost always, e.g. using a bucket name for a bucket object before the bucket exists). The actual creation operation will fire once all outputs-given-to-inputs are resolved.
b
So how do you pass Output<InputList> to Subnets on a LB creation?
If you have 
[Output] public StackSubnets {get; set]
t
The type for 
subnets
should be 
Output<ImmutableArray<string>>
. Also, you don’t need to make subnets the output of your stack, just declare a local variable.
Subnets = subnets
should work then
👍 1
2 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by