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

Related, if there’s a way to access it from the Automation API, that would be good too.

My sense from looking at the code is that there is no such way  - there’s no equivalent of setting/getting tags, or doing the equivalent of `pulumi stack ls --tag`

`pulumi stack tag set` and `pulumi stack tag ls` will let you set and list tags for a stack. But tags are a service concept, they aren't stored locally and won't work if using the filestate backend.
I don't think those commands are exposed directly in the automation api, but if you raise an issue they'd probably be pretty easy to add.

you can use the `--path` argument of `pulumi config set` or `pulumi config get` to manipulate config that uses your own namespacing

for instance `pulumi config set --path myorg.environment prod --stack {stackName}` would create a new `myorg` map in your config with a property `environment` and a value of `prod`

Right, but I can't do filtering when listing stacks based on config.

<@U02J3T6A8LB> there already seems to be an issue for over a year now btw :grinning:

<https://github.com/pulumi/pulumi/issues/5681|https://github.com/pulumi/pulumi/issues/5681>

Ah well up vote that then :slightly_smiling_face: I'm not sure where automation api currently is in priority but github votes _do_ influence the roadmap.

Yep, I have. :grinning:

But it seems the only way right now to programmatically interact with tags is through the REST API. 