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

There is `pulumi stack` and some flags to that to get more information. But not currently a full way to drill down into resources. 

We’ve actually been experimenting with a CLI-based resource explorer recently though. 

Curious - whats driving you to want to do this via CLI vs web?  Is it for scripting?  Or just a preference for staying in the CLI UX?  What key information are you looking for - property value, links to cloud consoles, something else?

Looking to easily validate targets before running commands. Looks like we found a workaround with `jq`

`pulumi stack export | jq '.deployment.resources[] | select(.urn|endswith("{instance name}")) | .outputs.tags.Name'`

Just an easy way to make sure you are looking at the right resource in a stack :slightly_smiling_face:

Ahh - got it - yes - `pulumi stack export` is good here.