terraform-exec VS Pulumi

You still have to call the terraform CLI, and as others suggested, terraform-exec is good (we use it with Lingon).

Debugging has actually been ok because all Lingon does is dump the HCL/YAML. For Kubernetes we shell out to kubectl and for Terraform we wrote a simple wrapper around terraform-exec that is not part of the core library. So when things go wrong, you're back to your basics.

I'm new to Go, and since I work pretty heavily with Terraform, I thought making some terraform automation with Go would be a great little side project/lab for learning. With that said, I'm wondering if anyone has had any luck using the terraform-exec library from hashicorp (https://github.com/hashicorp/terraform-exec). I'm finding the documentation incredibly hard to follow when trying to replicate some simple CLI commands like terraform plan and extract anything meaningful from it.

We will utilize this nice wrapper hashicorp/terraform-exec to apply the synthesized Terraform module from Go.

[hashicorp/terraform-exec sounds like what you're looking for if writing Go is okay](http://"GitHub - hashicorp/terraform-exec: Terraform CLI commands via Go." https://github.com/hashicorp/terraform-exec)

I am using a vendor from GitHub if I have to be specific this repo.

Hashicorp has their own module for doing this you might find useful: https://github.com/hashicorp/terraform-exec

If you are following this blog series, you should already know the benefits of using Terraform to define and deploy your AWS resources and configuration. Other IaC solutions such as AWS CloudFormation, AWS CDK, and Pulumi work the same way but differs in the programming or configuration language.

Infrastructure as Code (IaC) is an important part of any true hosting operation in the public cloud. Each of these platforms has their own IaC solution, e.g. AWS CloudFormation. But they also support popular open-source IaC tools like Pulumi or Terraform. A category of tools that also needs to be discussed is API gateways and other app-specific load balancers. There are applications for internal consumption, which can be called microservices if you have a lot of them. And often microservices use advanced networking options such as a service mesh instead of just the native private network offered by a VPC.

funny, to me systemd == no docker, no containers, just a VM.

it's my goto way to keep my programming running and have it be restarted if the vm reboots. I use VMs like "pods". I deploy code directly to the VM and run it there along with other programs. I scale up an scale down with: https://www.pulumi.com/

Pulumi — Modern infrastructure as a code platform that allows you to use familiar programming languages and tools to build, deploy, and manage cloud infrastructure.

A move like this may have an impact in other open source projects. Take Pulumi, for instance, people might avoid choosing it now that the Linux Foundation have its own IaC tool, and for newer, smaller projects it will probably be impossible to compete with a project under the Linux name.

Another alternative to writing an operator would be to rely on kustomize or https://www.pulumi.com/.

Pulumi

Would it make sense to say Dagger is to Pulumi [1], as Terraform is to Togomak?

[1]: https://www.pulumi.com/

Infrastructure as Code (IaC): Define your infrastructure using code (IaC) to automate the provisioning of resources such as virtual machines, load balancers, and databases. Tools like Terraform, Pulumi, and AWS CloudFormation can help.