Is your feature request related to a problem? Please describe.
With Vault 1.3 it is possible to use secondary_public_key on the API endpoint
/sys/replication/dr/primary/secondary-token. However, there is no further documentation on this.
(see https://www.vaultproject.io/api-docs/system/replication/replication-dr#secondary_public_key)
This is what the above website is currently showing:
`s

Thanks for this great tool!

Hoping to get some clarification here surrounding commits. I've setup automation around Gitleaks to scan commits as they happen on a few repositories, however, the tool is alerting when the secret is first committed, and then alerting a second time when it's removed (not a file deletion, but a line removal).

Is there any configuration options to disable alerts w

See https://github.com/square/keywhiz/blob/master/server/src/main/resources/keywhiz-development.yaml#L49

It's a dropWizard thing, but we should document why it exists in Keywhiz and how to configure it (or link to the DropWizard docs).

Since this has transitioned to using an in repo helm chart, the helm chart documentation should be checked, and documented. The current helm chart in this repo, seems to be built from several layers of templating which makes it harder to understand, and the correctness of this documentation all the more essential.

• The last Helm Stable repo version had the appropriate section documenting the

The regex test if [[ $yml =~ ^(.*/)?secrets(\.[^.]+)*\.yaml$ ]] does not match the helm secrets help text, at least on OSX.

secrets.dev.yaml functions properly; secrets-dev.yaml fails to decrypt; helm secrets implies it should: wrapper that decrypts secrets[.*].yaml

Starting at the "Create a staging environment", the steps described in the guide quickly outpace the explanations and it was not obvious to me what was going on. The quickstart assumes knowledge of concepts (environments, machines) that I would have liked to see brief explanations of.

The Quickstart could also use now.sh as an example deployment environment so that the user can follow along wit

Currently, the Consul random id is set to 16 bytes.
https://github.com/hashicorp/vault-guides/blob/master/operations/provision-vault/best-practices/terraform-aws/main.tf
(search for consul_encrypt)

In the Consul documentation, they recommend to use 32 bytes.
https://www.consul.io/docs/agent/options.html
(search for -encrypt)

As a Developer, I want to know why a Follower is not authenticating my application, so that I can address the issue without a lot of trial & error.

GIVEN an application deployed in K8s/OCP with the authenticator client
WHEN the the Follower rejects the authn request
THEN post the error message such that it is visible in the Follower log at the default log level.

Developer Notes

In /opt

How to combine this node client with plugins like MongoDB Database Plugin? I'd like to use it but I can't see any docs about that.

Note: Make sure to check out known issues (https://github.com/sparebankenvest/azure-key-vault-to-kubernetes#known-issues) before submitting

Describe the bug
Using environment injection with either the supplied test image or my own results in the container not starting, apparently because the expected volume mounts are not actually created.

AKS with kubernetes 1.17.0

**To Reproduc

I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|