Pulumi Corporation

And then maybe there's some way of configuring it, a YAML or like some kind of directional or even in code, if that's fine.

So similar to, you know, a Puppet versus a Pulumi or anything like, you know, you pick your poison to kind of control the system.

On the other hand, will we then have one factory, much like your CI-CD pipeline in a system or an enterprise, or will we have multiple? We'll probably have the same engine, but, you know, some of the workflow, some of the system, some of the tweaks we want to kind of express there as well.

And then will everybody go through the same process? There's value of going through the same process.

Maybe if that's custom or it's another tool like Terragrunt or one of the other mini tools out there.

What is the other, there's another tool out there, Pulumi? I wonder if this solves some of these problems.

I

wonder, yeah.

You declare what you want, you don't worry about how it gets done.

The platform takes care of that.

That's what Pulumi tries to do as well.

But yeah, Pulumi still has a managed state file outside of cloud and does not do continuous reconciliation.

There's a Terraform resource, Cloudflare _zero_trust_access_aicontrols_mcpportal.

It's in the Pulumi registry too.

It sets the host name, the per server tool, and prompt aliases, and the gateway routing toggle.

So the whole portal is declarative aside from the CNAME you create yourself.

... a character.

And the joke is it's supposed to be Jackie and I fighting, 'cause that was when she was at Hashi and I was at Pulumi.

And now we're neither of those places, so I guess we can be better friends.

It's a joke.

But let's, let's, let's get into it.

Speaking of tools, like various things like HashiCorp, Pulumi, all these kinds of things.

So as practitioners, as technologists, oh, my God, so many tools, and it just is getting worse.

I...

They wouldn't be caught dead with it.

Then you have, uh, Terraform of course, and you have Pulumi.

Pulumi is interesting because, uh, they've had staying power.

They've survived.

There have been a few other upstarts that have come around, and we also know like CDK TF, uh, that failed as a project.

Didn't work.

So we have these three staying powers.

Then the FOMO I have is should we be instead moving over to something more like Pulumi and TypeScript or picking the language du jour of our choice? And I keep coming back to I think it makes a lot of sense maybe inside of a enterprise where they might have more standardization on one or so languages.