7 ms·

I'm building a bunch of opinionated Ansible playbooks + tooling, with a Heroku-like experience.

• leetrout 6y ago
  I’m curious- why ansible instead of terraform for dealing with the cloud provider APIs for your base layer of infrastructure?
  • SingAlong 6y ago
    TBH because Ansible is what I’ve been using for a long time. And based on what FunnyLookinHat mentions in another comment, Terraform seems to offer a lot less. I have no first-hand experience with Terraform to confirm that.
    • leetrout 6y ago
      Yea it’s focused on the infrastructure layer. It has a separate state mechanism to keep things in sync that Ansible didn’t have the last time I tried only using Ansible. They’re a match made in heaven when put together IMO.
    • scaryclam 6y ago
      Terraform goes quite a lot further than FunnyLookinHat mentions. I actually don't advocate for using it further than infrastructure myself (I like using specific tooling for specific jobs), but that doesn't mean it can't go a lot further (https://www.terraform.io/docs/providers/index.html https://www.terraform.io/docs/providers/index.html for a list of the providers, and it's possible to use the null provider to write some more custom things and hack arounds). I've had a lot of success coupling Terraform with provisioners like Ansible or Saltstack. Of course, if Ansible is what you're used to and it works for you, there's no real benefit to using something else right now :) I'm a big fan of Terraform, so I hope you also have a play around with it to see if it can help with what you're doing in the future.