4 ms·
Hmmm i feel like those tools naturally railroad you into a certain split of responsibilities. Sure - you could use tf’s local/remote-exec to do the stuff you’d
by CraigJPerry 3y ago
Hmmm i feel like those tools naturally railroad you into a certain split of responsibilities.
Sure - you could use tf’s local/remote-exec to do the stuff you’d normally do with ansible but man that would be annoying and slow going when you know you can reach for ansible.
Vice versa, you could have an ansible playbook to call the cloud provider’s api and cook up some kind of approval workflow / state management but man that would be annoying and slow going when you know you can reach for terraform.
- TeMPOraL 3y agoDo they integrate that well? I don't have much experience with either, and until this moment I understood them to be substitutes - but still, I thought that: > you could have an ansible playbook to call the cloud provider’s api and cook up some kind of approval workflow / state management Was generally what people did before Terraform, and they be reluctant to add another complex tool, significantly overlapping with the current complex tool, just to simplify a part that already works OK. Conversely, if Terraform is really so amazing as one would believe reading HN, then some amount of "local/remoe-exec" pain seems justified if it lets you avoid bringing in Ansible with all its complexity? All these tools cost not just storage and processing, but also brain space. A Makefile in a cron, running some shell scripts, may be more brittle than whatever cookbooks or playbooks or ${what's the name for Terraform's flavor of makefiles}, but is also might be easier to fix when something breaks.