This message was deleted.
# general
s
This message was deleted.
w
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?
h
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 🙂
w
Ahh - got it - yes -
pulumi stack export
is good here.