This message was deleted.

Cc @colossal-beach-47527 who may know the answer to this.

It isn’t anything to be worried about. When you run

pulumi stack ls

we cap the results at 300 stacks returned. So if you are in an organization with many stacks you might need to narrow down your search by adding a project filter (

--project

), which should be inferred by the

Pulumi.yaml

file in the current directory. If you really want all the stacks, and don’t mind if the request takes a long while to serve, you can hit our REST API directly using something like:

curl \
    -H "Authorization: token ${PULUMI_ACCESS_TOKEN}" \
    "<https://api.pulumi.com/api/user/stacks?maxResults=600>"

(And you can specify other filters by passing

organization

,

project

,

tagName

, or

tagValue

URL query parameters.

@colossal-beach-47527 Thanks for the detailed answer. The API call helps a lot!! I would recommend adding the 300 Max to the documentation so users will not rely on it (as we did) with their automation tools.

I opened https://github.com/pulumi/pulumi/issues/3620 to track improving this. @best-waiter-16927 Feel free to add other notes there as well.

👍🙏