Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Terraform supports multiple vendors, but your templates are not vendor-neutral, you have to rewrite them all. I don't see it as that big a win over using each vendor's native tools, as long as they all support a config managed in git.


With terraform, I at least only have to learn one syntax, so there’s at least that, if noting else.


Which does little good if you still have to learn the provisioner, the terminology and the idiosyncrasies of the platform.

And good luck using your business support plan with AWS when something goes wonky and you’re using Terraform.


It does plenty of good. I have software that spans AWS, Azure, and GCP (don't ask me why). I can easily manage it as a cohesive whole, e.g. using an ip address provisioned in GCP as the target of a DNS record provisioned in AWS. I can spin it all up in a single call to a single tool.

Under the hood, terraform is just using the AWS APIs. If an error occurs with them, getting support isn't an issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: