Retry behavior without duplicate writes in Pulumi
Goal Determine how Pulumi’s retry mechanism prevents duplicate writes while maintaining consistency across multiple resources. Constraints Pulumi’s engine assumes provider idempotency; however, not all providers fully implement it, and the engine lacks cross‑resource transaction guarantees. A transient failure can leave the stack partially applied, and a sub