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

```const stack = await LocalWorkspace.selectStack({
  stackName: `${organization}/${stackName}`,
  projectName: project,
  program: async () =&gt; { }, // don't need a program just to get outputs
})

await stack.setAllConfig({ 'PULUMI_ACCESS_TOKEN': 'xxx' })

const outputsRes = await stack.outputs()```

PULUMI_ACCESS_TOKEN is an environment variable, not a conflg value.

Hi <@U012UJTT55M> - thanks for the response. Is it secure to set PULUMI_ACCESS_TOKEN as an environment variable in a container?

I believe so. This approach is used with many tools as a secure way to avoid putting secret values on the command line. The environment of one shell / process is well-protected from other processes.

This approach pre-dates Pulumi by many years...