Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Teller 2.0 does not support hashicorp namespace: #286

Open
romans-ovo opened this issue Jun 11, 2024 · 0 comments · May be fixed by #287
Open

Teller 2.0 does not support hashicorp namespace: #286

romans-ovo opened this issue Jun 11, 2024 · 0 comments · May be fixed by #287
Milestone
2.1

Comments

@romans-ovo
Copy link

romans-ovo commented Jun 11, 2024 •
edited
Loading

While it's possible to my tokens with this:

curl \
        --header "X-Vault-Token: $VAULT_TOKEN" \
       --header "X-Vault-Namespace: my-namespace" \
        --request GET \
        ${VAULT_ADDR}v1/secret/data/my-path

Teller does not offer an option to specify a namespace. a handy way would be like this:

providers:
  vault:
    kind: hashicorp
    options:
      namespace: my-namespace
    maps:
     - id: local
       path: my-path

vaultrs has support for namespaces since 2022:
jmgilman/vaultrs#41

I'm happy to submit PR for this.
@romans-ovo romans-ovo linked a pull request Jun 11, 2024 that will close this issue
Open
@jondot jondot added this to the 2.1 milestone Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.1
Development

Successfully merging a pull request may close this issue.

Add support for namespaces in kv2 / hashicorp romans-ovo/teller
2 participants
@jondot @romans-ovo