OpenTofu

Surprise, not a lot's changed.

They still use Terraform or OpenTOFU, all the things that they were using before.

are compatible with their APIs, but they also have MCP and CLI tools to manage this.

And once you get into their interface, you realize that part of what they can do because they're agnostic and they want to operationalize all of this across multi-clouds is they're setting up the Kubernetes distributions across the clouds for you.

So if you take YAML from six years ago and apply it today, you'll get the exact same artifact on top of any compute substrate, whether it's on-prem, Azure, etc.

We are...

When you say that, are we talking about your customers can continue to use Terraform or Pulumi? I'm assuming that that's how they're interacting with you, right? Like they're talking to your API from these particular management tools, right? I'm assuming OpenTOFU is supported.

What are the other ways? Because one of the things I've started to see with agents is if you're a singular cloud, it might just be better if your agent is the complete interface to whatever the description language is.

And oops, I hit cancel, hit yes, and there we go.

So this is using the JSON streaming capability, output streaming capability of Terraform and OpenTOFU to present a prettier console experience.

There's also another cool thing you can do with that setting.

I'm going to skip that for the moment and move on.

Now you can see there's more here to select from.

If I wanted to provision like the S3 bucket in the dev stack, I could enter.

Some of the interesting things happening now, you see it's automatically downloading Chekhov and OpenTOFU because those were declared as tool dependencies of the components.

Then it goes ahead and executes Chekhov as hooks for policy validation, and then opens Tofu, of course, to run the Terraform.

I usually generate some infrastructure as code with it.

You know, in the past, it's been OpenTofu, for example.

And then Claude generates that, and then I just run apply, and it just seems to work.

What are your thoughts on that?

So that's what we've done with Atmos.

Atmos supports today, Terraform, OpenTofu, Packer, Ansible, Helm, File, Helm, Kubernetes, containers, emulators.

You can even bring your own components.

And soon we're going to add CloudFormation to this list as a way of managing infrastructure.