limited-rainbow-5165008/15/2019, 8:22 PM
if you want replacements to delete first (increasing downtime, but allowing you to use the same id for the two resources). This is in general only a problem if you manually force the name of the resource to a specific value instead of relying on Pulumi's auto-naming (which would ensure the original and replacement don't conflict).
We are considering having explicit naming automatically change
to ease this process in the common case in https://github.com/pulumi/pulumi-terraform/issues/383.
limited-rainbow-5165008/15/2019, 8:40 PM
. The fact that this is the default in Pulumi ensures that you get effectively mini-blue/green deployments on every update. And in case something does fail - you are not in a state of your infrastructure being fundamentally broken (also the norm in Terraform deployments).
limited-rainbow-5165008/15/2019, 9:07 PM
attribute that came into the picture on TF resources?
is the default for all resources. Pulumi makes the
property optional on ~all resources, and automatically generates a name seeded from the Pulumi resource name with a random suffix. This accomplishes a similar goal as
, but again uses the safer approach as the default and applies this to everythign instead of only a handful of resources.
More on this here: https://www.pulumi.com/docs/reference/programming-model/#autonaming