So we'll use this thread to track "generic rolling updates to resources with count Just looked into this again and what make most sense to me (although I'm not very experienced with terraform, so let me know if this doesn't make sense) would be to create a terraform-side success condition.
Every resource could have a attribute which defines a condition built on top of 'remote-exec' which needs to return true for a resource update to success: If someone is interested I blogged on how we do immutable infrastructure and rolling upgrades (also of stateful services) here.
There's also an example of immutable infrastructure with consul and rolling upgrades in this github repository.
It can be obviously improved but we are quite happy with it.
Apparently the deployment-manager doesn't support it and apparently terraform can't help either.. Any rolling update facility we bake into Terraform wouldn't be ASG specific, so I'm going to merge this thread back down with #1552 and shift that issue to cover the general concept of rolling applies.
the ASG, that it might actually be reasonable to expect an ASG-specific feature there rather than one generic feature.
You can NOT update a shape in a stencil and have all drawings that used that shape update to the new version. Matt, I think I may have found a solution for this. I had the same issue but found that if I opened the 'Document Stencil' (instead of the masters stencil) and made changes to the masters in there it would update across the document when you clicked yes on the dialog.
In the interim, Paul Herber has a shape substitute utility. I don't know if it will change on all pages since I only had one page at the time however I cannot think of any reason why it shouldn't. When a shape is copied from a stencil to a drawing, a copy of the shape is placed in the local stencil.Between instance upgrades we have to do various pre and post actions and tests (for example to correctly handle #2957) so I'm not sure how all the different needs will fit inside terraform without breaking its declarative model.FYI: I've tried to use remote-exec provisioner and it doesn't work.When a symbol is obsolete you can update it or leave it in the schematic as is.However, if you choose to leave it as is, the design will not implement [email protected], we'll take a look as to whether @mwitkow we'd definitely love to figure out some sort of story for rolling updates in Terraform, it's just a matter of figuring out how to model the feature in a clean way that preserves our declarative model. Tagging this thread @mwitkow Even if it would be possible to create a new, then delete the old instance you still need to make sure the cluster is in sync before terminating the old instance and proceed with the next one.