https://pulumi.com
Join Slack
This message was deleted.
# dotnet
s
This message was deleted.
w
Copy code
var subnetCount = OutputUtilities.GetValueAsync(privateSubnetIds.Apply(ids => ids.Length)).GetAwaiter().GetResult();
for (var i = 0; i < subnetCount; ++i)
{
    new MountTarget($"{awsEksPrefix}-efs-mount-target-{i + 1}",
        new MountTargetArgs
        {
            FileSystemId = efsfileSystem.Id,
            SecurityGroups = { efsSecurityGroup.Id },
            SubnetId = privateSubnetIds.GetAt(i)
        },
        new CustomResourceOptions { Provider = awsProvider });
}
t
Indeed there’s no blessed way to iterate on an output of array outside 
apply
. The snippet above may work but I’m curious why you think it’s better than a loop inside apply?
b
i've had this same problem and similar solution, or sometimes just having to know the total count ahead of time. the reason is because you aren't supposed to create pulumi resources inside of an Apply, at least that is what I was mostly sure of
w
Which is the lesser evil? The above or creating resources inside apply? Is the latter to be avoided at all cost, or just a guideline?
t
Just a guideline. I expect them to behave similarly
w
Okay, but preview won't work for resources created in apply, right?
t
It will not show those resources initially, yes. I suppose it won’t work for your example either.
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