Diagnosing Pulumi Resource Drift from ignoreChanges Misconfiguration
Learn how to spot and fix Pulumi resource drift caused by an incorrectly configured ignoreChanges option.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to spot and fix Pulumi resource drift caused by an incorrectly configured ignoreChanges option.
Goal To guarantee that a schema change applied via Drift’s MigrationStep is atomic, so that if any step fails the database is rolled back to its original state. Constraints Drift’s migration API allows each step to run arbitrary SQL and may be asynchronous. The documentation states that a failure aborts the migration but does not automatically roll back chan