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.

Pulumi Community

Yep. Just await the first up, then run the 2nd up. You can use inline programs to make it clearer, but both methods work.

Here's an example of a go program that splits up a deployment across two stacks with automation api: <https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go>

First it deploys the <https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go#L79|bucket in one stack>, then it <https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go#L87|references that bucket as a stack output> and it feeds that bucketId into a function that <https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go#L96|generates the next program>. You can see here that the program for the object stack is <https://github.com/pulumi/automation-api-examples/blob/main/go/multi_stack_orchestration/main.go#L215|parameterized> to curry the bucketId.