vault
Here are 1,331 public repositories matching this topic...
Both parseInt and parseFloat take strings as arguments and convert them to 64 bit numbers of their appropriate type. The json.Number type is a string sub-type that contains integers or floats, but it causes a type error with the 2 parse functions. They should be change to accept json.Number fields and handle them appropriately.
Hi!
KES is officially deprecated
Are you a new user looking to start using KES?
Please take a look at the ESO instead!
KES = Kubernetes External Secrets (this repo)
ESO = External Secrets Operator (repo: external-secrets/external-secrets)
KES is under limited maintenance and the go rewrite ESO has c
When I use VScode to debug my python scripts, the settings cannot be load correctly, but it works fine when I directly run the scripts. How to solve this problem?
When directly run it prints correctly
 method.
However, for obvious reasons this will fail as it will attempt to list all mounted secrets engines (as it calls /v1/sys/mounts).
The web UI, however, shows what mounts the current token has access to.
While poking around the live API documentation the other day (`VAULT_BASE_URI/ui/vault/api-explorer
-
Updated
Mar 11, 2020 - Go
-
Updated
Jul 19, 2022 - Java
-
Updated
Jul 21, 2022 - Shell
-
Updated
Mar 10, 2017 - Perl
-
Updated
Jul 22, 2022 - Go
-
Updated
Jul 19, 2022 - Go
-
Updated
Aug 14, 2021 - HCL
In an effort to gather the list of users of argocd-vault-plugin, we are asking that if you are a user of AVP, please add your organization to our users list! https://github.com/IBM/argocd-vault-plugin/blob/main/USERS.md.
This helps us understand where and how AVP is being used so we can continuously improve the project.
Thank you!
-
Updated
Jun 8, 2022 - Go
-
Updated
Apr 24, 2022 - JavaScript
-
Updated
Oct 17, 2021
Improve this page
Add a description, image, and links to the vault topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vault topic, visit your repo's landing page and select "manage topics."

So pretty weird issue:
I am creating 2 prefixes, one empty, one not empty like this...
then when I curl those prefixes recursively like:
notice how only testprefix/ is specifically listed?
now