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

You can use the pulumi cli to write out stack outputs as a json blob, e.g:
```$ pulumi stack output --json --stack dev
{
  "bucketName": "my-bucket-026fb45",
  "codeId": "arn:aws:codebuild:us-west-1:616138583583:project/project-ba84a1b"
}```

hmm I ran that command but it says stack dev cant be found? but i have a dev stack.

I fixed this by running pulumi stack select dev -c, so now the command doesn't error out.

Note I have not yet defined output variables. Maybe its a bug in the cli.

ah looking at the vstacks the first was gurdips1/dev

Yeh it might not of been able to auto fill the project name depending on what your directory was when you ran `stack output`

This raises a few Questions. When I am running pulumi commands, I notice a lot of them don't speicfy a project name. So presumably should be run in the directory of the project?

with the stack output command, the output variable is a secret, how can I get the actual plaintext value?

They don't have to be run from the project directory, but if you run them from elsewhere you need to tell it which project you mean. If you run it from the project directory the cli can auto-fill the project name based on the Pulumi.yaml it finds.

```$ pulumi stack export --help
...
      --show-secrets false   Emit secrets in plaintext in exported stack. Defaults to false```


ah gotcha! That's helpful on both of my questions. On another note, I deployed my first pulumi program and was a breeze.