No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

is there an automation api to list all stacks for a project?

Not an automation API, but if you are using the Pulumi hosted service as your state backend, you can use their official API: <https://www.pulumi.com/docs/reference/service-rest-api/#list-stacks>

aww bummer. alright. no im not using that. guess I can shell out for that for now.

Why shell out? With Pulumi, you are using code, which means you can use any http library to perform requests against that API.

Because I'm not using the pulumi service?

Sorry, overlooked that in your previous answer.

Which state backend are you using? And which programming language are you using for Pulumi code?

In your setup, I still would not shell out, but go for a coding approach in which you use the `aws-sdk` library to iterate over the s3 folders in your state bucket:
<https://www.npmjs.com/package/aws-sdk>

Am I being a dummy and misunderstanding the question or does Automation API actually support this? <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/automation/#Workspace-listStacks>

It does -- here's the same docs for Golang <https://pkg.go.dev/github.com/pulumi/pulumi/sdk/v3/go/auto#Workspace.ListStacks>

<@U01E602D5JA> nice yeah! Very funny to see the actual implementation is exactly how I did it xD

Im unsure how to use that call though. Doesn't seem to be available on `LocalWorkspace` anyways. I am using it like this atm:

```const stack = await LocalWorkspace.createOrSelectStack(args);```


It is not a static function it is an instance function. You must first instantiate a workspace instance

Your example is like a helper function to bypass creating a workspace instance and get a stack instance in one line, but you could either access the workspace with stack.Workspace after doing that or not instantiate a stack and simply instantiate a workspace instead