Merge pull request #6545 from kamolhasan/docs_gcp_secret_engine

Correct gcp api doc
This commit is contained in:
Becca Petrin 2019-04-08 09:53:28 -07:00 committed by GitHub
commit c39476ade5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -265,7 +265,7 @@ $ curl \
| Method | Path |
| :----------------------------- | :------------------------ |
| `GET` | `POST` | `/gcp/token/:roleset` |
| `GET` / `POST` | `/gcp/token/:roleset` |
Generates an OAuth2 token with the scopes defined on the roleset. This OAuth access token can
be used in GCP API calls, e.g. `curl -H "Authorization: Bearer $TOKEN" ...`
@ -284,7 +284,7 @@ do not apply.
$ curl \
--header "X-Vault-Token: ..." \
--request GET \
https://127.0.0.1:8200/v1/consul/gcp/roleset/my-token-roleset
https://127.0.0.1:8200/v1/gcp/token/my-token-roleset
```
### Sample Response
@ -308,7 +308,7 @@ $ curl \
| Method | Path |
| :----------------------------- | :------------------------ |
| `GET` | `POST` | `/gcp/key/:roleset` |
| `GET` / `POST` | `/gcp/key/:roleset` |
If using `GET` ('read'), the optional parameters will be set to their defaults. Use `POST` if you
want to specify different values for these params.
@ -340,7 +340,7 @@ or the system default if config was not defined.
$ curl \
--header "X-Vault-Token: ..." \
--request GET \
https://127.0.0.1:8200/v1/gcp/roleset/my-token-roleset
https://127.0.0.1:8200/v1/gcp/key/my-key-roleset
```
```sh
@ -348,7 +348,7 @@ $ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
https://127.0.0.1:8200/v1/gcp/roleset/my-token-roleset
https://127.0.0.1:8200/v1/gcp/key/my-key-roleset
```
### Sample Response