From 55993e7a0a9daadc463e8b2104deec867d630d51 Mon Sep 17 00:00:00 2001 From: Dave Henderson Date: Sat, 19 Nov 2016 18:46:48 -0500 Subject: Adding support for GitHub auth strategy for Vault datasources Signed-off-by: Dave Henderson --- README.md | 1 + 1 file changed, 1 insertion(+) (limited to 'README.md') diff --git a/README.md b/README.md index c21fe347..1536b427 100644 --- a/README.md +++ b/README.md @@ -582,6 +582,7 @@ This table describes the currently-supported authentication mechanisms and how t | auth backend | configuration | | ---: |--| | [`app-id`](https://www.vaultproject.io/docs/auth/app-id.html) | Environment variables `$VAULT_APP_ID` and `$VAULT_USER_ID` must be set to the appropriate values.
If the backend is mounted to a different location, set `$VAULT_AUTH_APP_ID_MOUNT`. | +| [`github`](https://www.vaultproject.io/docs/auth/github.html) | Environment variable `$VAULT_AUTH_GITHUB_TOKEN` must be set to an appropriate value.
If the backend is mounted to a different location, set `$VAULT_AUTH_GITHUB_MOUNT`. | | [`token`](https://www.vaultproject.io/docs/auth/token.html) | Determined from either the `$VAULT_TOKEN` environment variable, or read from the file `~/.vault-token` | To use a Vault datasource with a single secret, just use a URL of -- cgit v1.2.3