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’t use the Pulumi SDK outside of a Pulumi program. you need to use the automation API in order to do that

Thanks <@UCWG26BH7> ! Such speed! Any pointers / sample code already out there?

<https://github.com/pulumi/automation-api-examples/tree/main/dotnet>

you may just find it easier to run `pulumi stack output --show-secrets -s "myorg/mystack/dev"` as an executable in your program if you only need to get the stack reference

<@UCWG26BH7> thanks! It does not look like 'pulumi login' is supported by the automation api right?  Is there a way to auth with an access token without relying on the pulumi cli?

`pulumi login` just builds a `~/.pulumi/credentials.json` like this

```{
  "current": "<https://api.pulumi.com>",
  "accessTokens": {
    "<https://api.pulumi.com>": &lt;redacted&gt;
  },
  "accounts": {
    "<https://api.pulumi.com>": {
      "accessToken": &lt;redacted&gt;,
      "username": "jaxxstorm",
      "organizations": [
        "jaxxstorm",
        "lbrlabs",
        "team-ce",
        "demo",
        "pulumi"
      ],
      "lastValidatedAt": "2022-07-12T17:32:23.907266-07:00"
    }
  }
}```
You can just create that file and write it yourself :slightly_smiling_face:

you will need the pulumi cli for most operations though, it’s the on;y effective way to talk to the engine

Sweet, thanks a lot. Yes I used the Pulumi cli a lot for deploying the infrastructure. Now putting together a lightweight app for a tech to provision that infrastructure, trying to keep the dependencies/extra steps as little as possible

if you’re not using the automation API, it’s going to make your life much much easier :smile: