mirror of
https://github.com/hashicorp/vault-action.git
synced 2025-11-07 07:06:56 +00:00
docs: add namespace example to readme
This commit is contained in:
parent
148ee648cc
commit
3224a223d4
1 changed files with 19 additions and 1 deletions
20
README.md
20
README.md
|
|
@ -486,7 +486,6 @@ steps:
|
||||||
uses: hashicorp/vault-action
|
uses: hashicorp/vault-action
|
||||||
with:
|
with:
|
||||||
url: https://vault-enterprise.mycompany.com:8200
|
url: https://vault-enterprise.mycompany.com:8200
|
||||||
caCertificate: ${{ secrets.VAULT_CA_CERT }}
|
|
||||||
method: token
|
method: token
|
||||||
token: ${{ secrets.VAULT_TOKEN }}
|
token: ${{ secrets.VAULT_TOKEN }}
|
||||||
namespace: admin
|
namespace: admin
|
||||||
|
|
@ -496,6 +495,25 @@ steps:
|
||||||
secret/data/ci npm_token
|
secret/data/ci npm_token
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Alternatively, you may need to authenticate to the root namespace and retrieve
|
||||||
|
a secret from a different namespace. To do this, do not set the `namespace`
|
||||||
|
parameter. Instead set the namespace in the secret path. For example, `<NAMESPACE>/secret/data/app`:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
steps:
|
||||||
|
# ...
|
||||||
|
- name: Import Secrets
|
||||||
|
uses: hashicorp/vault-action
|
||||||
|
with:
|
||||||
|
url: https://vault-enterprise.mycompany.com:8200
|
||||||
|
method: token
|
||||||
|
token: ${{ secrets.VAULT_TOKEN }}
|
||||||
|
secrets: |
|
||||||
|
namespace-1/secret/data/ci/aws accessKey | AWS_ACCESS_KEY_ID ;
|
||||||
|
namespace-1/secret/data/ci/aws secretKey | AWS_SECRET_ACCESS_KEY ;
|
||||||
|
namespace-1/secret/data/ci npm_token
|
||||||
|
```
|
||||||
|
|
||||||
## Reference
|
## Reference
|
||||||
|
|
||||||
Here are all the inputs available through `with`:
|
Here are all the inputs available through `with`:
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue