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.

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

Reading a secret from vault #28

Open
Rand0mF opened this issue Feb 9, 2024 · 0 comments
Open

Reading a secret from vault #28

Rand0mF opened this issue Feb 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Rand0mF
Copy link

Rand0mF commented Feb 9, 2024

What happened?

I want to read a secret from vault, only watching it, not taking control of it.
Not 100% sure if this provider is meant to do that, as it's lacking documentation. Though I think it should be, as the terraform module it is based on can do that.
From the API it looks like it could be possible but every Secret object requires dataJsonSecretRef (for writing the secret).

Though the API documentation does not label this field as mandatory, in fact it is as following error occurs when applying without it:

The Secret "test" is invalid: spec: Invalid value: "object": dataJsonSecretRef is a required parameter

How to reproduce:

apiVersion: generic.vault.upbound.io/v1alpha1
kind: Secret
metadata:
  name: test
spec:
  forProvider:
    path: "kv/some/path"
  providerConfigRef:
    name: vault-provider-config

What environment did it happen in?

Version 0.3.0 of the provider.

@Rand0mF Rand0mF added the bug Something isn't working label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant