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

i’m trying to figure out the best pattern for updating a resource after creation, based on the creation of other resources. see the thread for a specific use case.

<https://neon.com/docs/guides/neon-private-networking>

i need to create a VPC Endpoint with privateDnsEnabled = false, create some resources in Neon, and then set privateDnsEnabled = true.

That's an imperative problem, not suited to a declarative solution like Pulumi. If I had this problem, I would define the desired end state in Pulumi and `up` it, then put an `up` freeze in place (so that Pulumi doesn't change anything) and run the imperative steps. Afterwards, run `pulumi refresh` and/or `pulumi up`, as needed.

The imperative steps would be outside Pulumi. Stick to their knitting!