11–20 of 167 posts
I’m a little unclear on terraform in practice. As you supposed to download this, use it’s language and syntax which is all it’s own thing, to define you services and then export that to a YAML setup that AWS CloudFormation (for example) is expecting? I assume there are reasons I wouldn’t just define it myself in YAML directly?
I’m a little unclear on terraform in practice. As you supposed to download this, use it’s language and syntax which is all it’s own thing, to define you services and then export that to a YAML setup that AWS CloudFormation (for example) is expecting? I assume there are reasons I wouldn’t just define it myself in YAML directly?
I’m a little unclear on terraform in practice. As you supposed to download this, use it’s language and syntax which is all it’s own thing, to define you services and then export that to a YAML setup that AWS CloudFormation (for example) is expecting? I assume there are reasons I wouldn’t just define it myself in YAML directly?
Basically Terraform is cloud agnostic, so you can (theoretically) define something in Terraform and then use it on AWS, or GCP, or Azure.
Terraform supports each of those providers, but the resources are specific to each provider.
You cannot use the same Terraform configuration on AWS and Azure.
Nor would you want to, per se. As far as I know, this is by design.
My biggest hope is that this means that some effort can be directed back to fixing bugs. I love what terraform can do, but I hate what I sometimes need to write to make it work. Also, I'll go out on a limb and say that I dislike the flexibility of iteration allowed in HCL 2. I know that people overwhelmingly asked for it, but my opinion is that it demonstrates a fundamental misunderstanding of how the v. 11 and earli…
The biggest issue we have with Terraform (and other Hashicorp tools in general, really) is their different configuration formats, but mostly it is HCL limitations. I haven't found a solution for it, but I have lots of resources that are almost identical, except for a few arguments, but right now it seems like my options are to either write my own Ruby script to output .hcl files, or live with two resources that are a…
I’m a little unclear on terraform in practice. As you supposed to download this, use it’s language and syntax which is all it’s own thing, to define you services and then export that to a YAML setup that AWS CloudFormation (for example) is expecting? I assume there are reasons I wouldn’t just define it myself in YAML directly?
The state of the infrastructure is stored, ideally, in the cloud. You apply your code during which terraform identifies which changes need to be made by comparing the current state with your local changes and executes those changes as you watch.
The end result is well-defined, testable, repeatable cloud infrastructure provisioning.
Infrastructure as code. Store it in git. Profit.
Earlier quoted context omitted.
Basically Terraform is cloud agnostic, so you can (theoretically) define something in Terraform and then use it on AWS, or GCP, or Azure.
That's not at all how it works. Terraform supports each of those providers, but the resources are specific to each provider. You cannot use the same Terraform configuration on AWS and Azure. Nor would you want to, per se. As far as I know, this is by design.
[1] https://app.terraform.io/signup?utm_source=banner&utm_campai...
Earlier quoted context omitted.
That's not at all how it works. Terraform supports each of those providers, but the resources are specific to each provider. You cannot use the same Terraform configuration on AWS and Azure. Nor would you want to, per se. As far as I know, this is by design.
Fair criticism, I've never used it, just what I've picked up from their marketing material.
> Fair criticism, I've never used it, just what I've picked up from their marketing material.
LOL, why'd you even comment? You are making statements based on marketing material? Microsoft is probably hiring people like you if you're looking for a job.