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

Maybe `ignoreChanges` and/or `customTimeouts`

• <https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/>
• <https://www.pulumi.com/docs/intro/concepts/resources/options/customtimeouts/>
"bad practice" depends on your use case, you might need a separate process to ensure it finished provisioning successfully.

ok. I’m sorry I should have said not wait. If we change and use the setting you’re talking we will ignore the change. That is not what we want. The second will just make it crash…