3 ms·
This is effectively the 'dry-run' feature that has been sought for a long long time [1], and led me to switch to Terraform (which does do this amongst other key
by leg100 11y ago
This is effectively the 'dry-run' feature that has been sought for a long long time [1], and led me to switch to Terraform (which does do this amongst other key differences) . Why did it take so damn long to implement?
I do appreciate it has come about eventually. Terraform has its foibles (and stupid half-declarative language) but it would take further improvements to consider going back to CF.
[1] https://forums.aws.amazon.com/thread.jspa?messageID=563929򉫙 https://forums.aws.amazon.com/thread.jspa?messageID=563929&#...
- zwily 11y agoActually, this isn't quite dry-run. What this does is calculate the diff between two templates, and just provide the operations from that diff. It does not inspect the current state of resources to see if there were any out-of-band changes that would be unwound. So it gets you closer to a dry-run, but is not as complete as terraform's.