a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
157 lines
4 KiB
Markdown
157 lines
4 KiB
Markdown
---
|
||
layout: "api"
|
||
page_title: "Cubbyhole - Secrets Engines - HTTP API"
|
||
sidebar_title: "Cubbyhole"
|
||
sidebar_current: "api-http-secret-cubbyhole"
|
||
description: |-
|
||
This is the API documentation for the Vault Cubbyhole secrets engine.
|
||
---
|
||
|
||
# Cubbyhole Secrets Engine (API)
|
||
|
||
This is the API documentation for the Vault Cubbyhole secrets engine. For
|
||
general information about the usage and operation of the Cubbyhole secrets
|
||
engine, please see the
|
||
[Vault Cubbyhole documentation](/docs/secrets/cubbyhole/index.html).
|
||
|
||
This documentation assumes the Cubbyhole secrets engine is enabled at the
|
||
`/cubbyhole` path in Vault. Since it is possible to enable secrets engines at
|
||
any location, please update your API calls accordingly.
|
||
|
||
## Read Secret
|
||
|
||
This endpoint retrieves the secret at the specified location.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `GET` | `/cubbyhole/:path` | `200 application/json` |
|
||
|
||
### Parameters
|
||
|
||
- `path` `(string: <required>)` – Specifies the path of the secret to read.
|
||
This is specified as part of the URL.
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
http://127.0.0.1:8200/v1/cubbyhole/my-secret
|
||
```
|
||
|
||
### Sample Response
|
||
|
||
```json
|
||
{
|
||
"auth": null,
|
||
"data": {
|
||
"foo": "bar"
|
||
},
|
||
"lease_duration": 0,
|
||
"lease_id": "",
|
||
"renewable": false
|
||
}
|
||
```
|
||
|
||
## List Secrets
|
||
|
||
This endpoint returns a list of secret entries at the specified location.
|
||
Folders are suffixed with `/`. The input must be a folder; list on a file will
|
||
not return a value. The values themselves are not accessible via this command.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `LIST` | `/cubbyhole/:path` | `200 application/json` |
|
||
|
||
### Parameters
|
||
|
||
- `path` `(string: <required>)` – Specifies the path of the secrets to list.
|
||
This is specified as part of the URL.
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request LIST \
|
||
http://127.0.0.1:8200/v1/cubbyhole/my-secret
|
||
```
|
||
|
||
### Sample Response
|
||
|
||
The example below shows output for a query path of `cubbyhole/` when there are
|
||
secrets at `cubbyhole/foo` and `cubbyhole/foo/bar`; note the difference in the
|
||
two entries.
|
||
|
||
```json
|
||
{
|
||
"auth": null,
|
||
"data": {
|
||
"keys": ["foo", "foo/"]
|
||
},
|
||
"lease_duration": 2764800,
|
||
"lease_id": "",
|
||
"renewable": false
|
||
}
|
||
```
|
||
|
||
## Create/Update Secret
|
||
|
||
This endpoint stores a secret at the specified location.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `POST` | `/cubbyhole/:path` | `204 (empty body)` |
|
||
| `PUT` | `/cubbyhole/:path` | `204 (empty body)` |
|
||
|
||
### Parameters
|
||
|
||
- `path` `(string: <required>)` – Specifies the path of the secrets to
|
||
create/update. This is specified as part of the URL.
|
||
|
||
- `:key` `(string: "")` – Specifies a key, paired with an associated value, to
|
||
be held at the given location. Multiple key/value pairs can be specified, and
|
||
all will be returned on a read operation. A key called `ttl` will trigger some
|
||
special behavior; see above for details.
|
||
|
||
### Sample Payload
|
||
|
||
```json
|
||
{
|
||
"foo": "bar",
|
||
"zip": "zap"
|
||
}
|
||
```
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request POST \
|
||
--data @payload.json \
|
||
http://127.0.0.1:8200/v1/cubbyhole/my-secret
|
||
```
|
||
|
||
## Delete Secret
|
||
|
||
This endpoint deletes the secret at the specified location.
|
||
|
||
| Method | Path | Produces |
|
||
| :------- | :--------------------------- | :--------------------- |
|
||
| `DELETE` | `/cubbyhole/:path` | `204 (empty body)` |
|
||
|
||
### Parameters
|
||
|
||
- `path` `(string: <required>)` – Specifies the path of the secret to delete.
|
||
This is specified as part of the URL.
|
||
|
||
### Sample Request
|
||
|
||
```
|
||
$ curl \
|
||
--header "X-Vault-Token: ..." \
|
||
--request DELETE \
|
||
http://127.0.0.1:8200/v1/cubbyhole/my-secret
|
||
```
|