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

Can you split the project into two? One that prepares the integration, and one that uses it?

The integrationKey property is available on the resource. It's listed under inputs, because it can be provided or generated.

Hey <@U012UJTT55M>, thanks for the answer. I ended up generating the `integrationKey` on my side just like you said and provided it as part of the resource, but I was curious if there's a feature on Pulumi supporting the `depends_on` functionality between a resource and a getter

Those getters aren't really getters, they're nice wrappers around the SDK. They don't return resources, they just return dependency-less results objects. Therefore, they probably don't honour the dependsOn opt.

For some reason, the InvokeOptions link isn't taking me anywhere, so I can't confirm what type it is even...

You can use ServiceIntegration.get(), which will honour the dependsOn option.

But if the integrationKey is really output from the ServiceIntegration resource when it's not provided as an input, then that's the way to go in this case. If it's not, then what you did is best.