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

(kv) secret's value can be of any type, but safe forces string #238

Open
maxenced opened this issue Dec 20, 2023 · 1 comment
Open

(kv) secret's value can be of any type, but safe forces string #238

maxenced opened this issue Dec 20, 2023 · 1 comment

Comments

@maxenced
Copy link

As per

data map[string]string
, it seems a secret can only has string value. However, as described here : https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2

Key names must always be strings. If you write non-string values directly via the CLI, they will be converted into strings. > However, you can preserve non-string values by writing the key/value pairs to Vault from a JSON file or using the HTTP API.

Right now, safe import fails if you give anything but a string, with, for ex :
!! json: cannot unmarshal bool into Go value of type string

@wirwolf
Copy link

wirwolf commented Nov 11, 2024

Have the same problem

wirwolf added a commit to SomeBlackMagic/vault-secret-editor that referenced this issue Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants