Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[concepts/options/deleteBeforeReplace] Typo fix + consistency warnings #13980

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+1 −1
Open

[concepts/options/deleteBeforeReplace] Typo fix + consistency warnings #13980

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
18435cf
s/dependencies/dependents
lukealbao Feb 5, 2025
780505d
Additional consistency warnings
lukealbao Feb 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/docs/iac/concepts/options/deletebeforereplace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ aliases:

A resource may need to be replaced if an immutable property changes. In these cases, cloud providers do not support updating an existing resource so a new instance will be created and the old one deleted. By default, to minimize downtime, Pulumi creates new instances of resources before deleting old ones.

Setting the `deleteBeforeReplace` option to true means that Pulumi will delete the existing resource before creating its replacement. Be aware that this behavior has a cascading impact on dependencies so more resources may be replaced, which can lead to downtime. However, this option may be necessary for some resources that manage scarce resources behind the scenes, and/or resources that cannot exist side-by-side.
While Setting the `deleteBeforeReplace` option may be necessary for some resources that manage scarce resources behind the scenes, and/or resources that cannot exist side-by-side, be aware that it introduces some risks. Since this behavior has a cascading impact on dependents so more resources may be replaced, it can lead to downtime. Separately, consider the consistency guarantees offered by your Cloud Providers. For example, AWS's APIs are all eventually consistent. In some scenarios, it is possible to create corrupted dependent resources because the dependency deletion has not propagated before the dependent's creation is executed.

This example deletes a database entirely before its replacement is created:

Expand Down