vault
Here are 859 public repositories matching this topic...
-
Updated
Sep 2, 2020 - Go
-
Updated
Sep 4, 2020 - Java
-
Updated
Aug 19, 2020 - Go
-
Updated
Aug 29, 2020 - Python
Is your feature request related to a problem? Please describe.
Investigate github.com/google/go-containerregistry to replace the heroku/docker-registry-client which seems to be unmaintained.
Describe the solution you'd like
Check the go-containerregistry library and see if it fits our needs.
Describe alternatives you've considered
We already use a forked version of the docker-
I am on 4.2.0, and i get cannot get a v2 secret with 1 or 2 set for this. Both give the same error
{"level":50,"time":1594786938370,"pid":17,"hostname":"external-secrets-do-kubernetes-external-secrets-7bcb5d65fb4qdn4","response":{"statusCode":404,"body":{"request_id":"670b25b7-36ef-8888-d214-05a09271b72e","lease_id":"","renewable":false,"lease_duration":0,"data":null,"wrap_info":null,"warnin
-
Updated
Sep 5, 2020 - Go
When specifying a vault URL, it should be possible to request round-robin discovery if the first returned vault is still sealed.
i.e.
http://vault.example.org might resolve to several addresses 10.11.11.2,10.11.11.4,10.11.11.5,10.11.11.6,10.11.11.7.
Currently if the client gets handed 1 address by DNS and it happens to be sealed, an exception is thrown. It would be convenient if the c
-
Updated
Mar 11, 2020 - Go
-
Updated
Jul 15, 2020 - Go
-
Updated
Mar 10, 2017 - Perl
-
Updated
Sep 4, 2020 - HCL
-
Updated
Sep 4, 2020 - Java
-
Updated
Aug 3, 2020 - JavaScript
-
Updated
Apr 6, 2018 - Python
-
Updated
Sep 4, 2020 - Java
-
Updated
Feb 4, 2020 - HTML
-
Updated
Aug 19, 2020 - Go
-
Updated
Feb 18, 2019 - Go
-
Updated
Sep 1, 2020
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."


We were using CGO with our ARM builds due to this bug... golang/go#32912
Which was fixed in go1.14. So we can remove this workaround.
The workaround was initially implemented here.. hashicorp/consul-template@d1e1dad
Just need to remove the special cases for ARM.