Hey all, I was looking at interacting with Pulumi Cloud via the Rest API and was looking around. I see that we have at some (all?) of that rest client already built for use with go but it is an internal package here. Any possibility of extracting that out into a pulumi go client?

It's wrapped with a normal Pulumi provider, will that do? https://www.pulumi.com/registry/packages/pulumiservice/

We have been talking about some of those options lately, mainly in the context of providing an ESC SDK but it could apply to the rest of Pulumi cloud as well.

I was thinking about how Engin had used the pinecone Openapi spec to generate the client for that provider. At least that is what I think he did and it sounded super helpful

We have been experimenting with an Open API spec for just ESC. Not everything that you can do in ESC has OpenAPI support but we have been able to work around most of that. The other APIs we could do in a similar fashion. It would be helpful if you had some use cases you were looking to the API to solve so we could prioritize (I think if we try to expose the entire surface area in one go it will slow us down).

I was looking to automate the setup of the deployments from within commands from our cli

Hello @brash-gigabyte-81569, I guess you opened a ticket for the OpenAPI spec yesterday, but there already was one: https://github.com/pulumi/pulumi-cloud-requests/issues/100

Got a little overzealous and created it without searching 😐, just closed mine

No problem.

@enough-architect-32336 One specific thing I am looking to do which doesn’t seem like it is exposed yet is to configure the customer managed deployment runner pool to use for a deployment

Ah you are right that is not exposed yet

I was able to capture the calls and build out the api https://github.com/pulumi/pulumi-pulumiservice/pull/228