is there a way to tell pulumi to not way on the resource modifcation? I’m deploying an opensearch resources and the updates take time because of the rollout procedure and make my ci pipeline to nuts. If yes, does it’s a bad practice?

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…