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

Hey!
```pulumi stack init my-stack \
    --secrets-provider="<hashivault://payroll>"```
Command above works fine when I set env variable `VAULT_TOKEN`. However, id does not work when `VAULT_TOKEN`
is unset and instead I have token in my `~/.vault-token`.

Is it possible to make pulumi work with `~/.vault-token`  ?

It doesn't appear to be supported. Could you please open an issue here <https://github.com/pulumi/pulumi-service/issues/new/choose> ?

it wouldn’t be a service issue. The authentication is handled by this library: <https://github.com/google/go-cloud>

filing an issue there is the first step

<@UCWG26BH7> just want to confirm. The library that is use for `pulumi up/preview/destroy` have nothing to do with <https://github.com/pulumi/pulumi-vault|pulumi_vault>, right ?

no, the provider binary and the cli binary operate differently and handle authentication differently

the cli talks to the provider via GRPC (via localhost), so they auth independently from each other

and Pulumi team use <https://github.com/google/go-cloud|go-cloud> for this

go-cloud is used for the self managed secrets providers and the self managed backends

it’s NOT used for the `pulumi_vault` provider

yeah, I am asking about self managed secret provider.

I was confused that configs like `vault:address` and `vault:namespace` would work. but, that’s not the case