3 ms·
From the problems the author is having, it would appear that perhaps Pulumi would be the better choice in this case.
by bovermyer 5y ago
From the problems the author is having, it would appear that perhaps Pulumi would be the better choice in this case.
- rgoulter 5y agoIn the article, the problems the author discusses are: 1. Inconsistent behaviour between providers. e.g. if a resource has been destroyed since the last `terraform apply`, then some resources/providers would recreate the resource, others wouldn't. (Similarly, there's not a guarantee that the state after running `terraform apply` matches up with what's there, if the provider is happy with its state file). 2. The dependencies of already-applied resources can block `terraform apply` if the upstream API for these resources suffers an outage. 3. If a `terraform apply` applies some resources before failing, this can result in an inconsistent state. Either the resources need to be deleted, or imported. I'm not familiar with Pulumi; what aspects of these would Pulumi help with?
- kall 5y ago3 happens regularly and I don‘t see how the other two would really be different, since some pulumi providers are using terraform providers under the hood.