News for hackers. Stuff that matters.
Re:AWS services to avoid by scarface74 on Sunday May 10, 2020 @07:46AM (#23131912)
Terraform is not “cloud agnostic”. Every provisioner is specific to the platform.
Re:AWS services to avoid by ciguy on Sunday May 10, 2020 @08:27AM (#23132093)
Perhaps bad terminology on my part but I would argue that Terraform IS cloud agnostic, it is NOT cloud portable.

You can use Terraform with any cloud. You cannot seamlessly move your AWS configuration to Google Cloud but you can still write Google Cloud configuration with the same paradigm as your AWS configuration.

Re:AWS services to avoid by jen20 on Sunday May 10, 2020 @08:40AM (#23132157)
This is exactly the idea of Terraform - the workflow is portable and agnostic, but the full fidelity of each individual resource provider API is exposed.
Re:AWS services to avoid by jatone on Sunday May 10, 2020 @08:54AM (#23132246)
which is fantastic. =)
Re:AWS services to avoid by eraad on Sunday May 10, 2020 @09:19AM (#23132366)
At first I read: Every prisoner is specific to the platform. It seems to clarify the point anyways.
Re:AWS services to avoid by pepemon on Sunday May 10, 2020 @07:57AM (#23131965)
Right, but the HCL syntax and overall Terraform paradigm is not.
Re:AWS services to avoid by rantwasp on Sunday May 10, 2020 @11:46AM (#23133511)
it’s not just the provisoner. it’s. it like different clouds have the same abstraction. for all intents and purposes you need to understand the underlying cloud and how to use api/tooling around it when terraform fucks up