mirror of
https://github.com/hashicorp/vault.git
synced 2025-09-01 20:11:09 +02:00
a43e292424
* 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
2.3 KiB
2.3 KiB
layout, page_title, sidebar_title, sidebar_current, description
| layout | page_title | sidebar_title | sidebar_current | description |
|---|---|---|---|---|
| api | /sys/control-group - HTTP API | <tt>/sys/control-group</tt> | api-http-system-control-group | The '/sys/control-group' endpoint handles the Control Group workflow. |
Authorize Control Group Request
~> Enterprise Only – These endpoints require Vault Enterprise.
This endpoint authorizes a control group request.
| Method | Path | Produces |
|---|---|---|
POST |
/sys/control-group/authorize |
200 (application/json) |
Parameters
accessor(string: <required>)– The accessor for the control group wrapping token.
Sample Payload
{
"accessor": "0ad21b78-e9bb-64fa-88b8-1e38db217bde",
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/control-group/authorize
Sample Response
{
"data": {
"approved": false
}
}
Check Control Group Request Status
This endpoint checks the status of a control group request.
| Method | Path | Produces |
|---|---|---|
POST |
/sys/control-group/request |
200 (application/json) |
Parameters
accessor(string: <required>)– The accessor for the control group wrapping token.
Sample Payload
{
"accessor": "0ad21b78-e9bb-64fa-88b8-1e38db217bde",
}
Sample Request
$ curl \
--header "X-Vault-Token: ..." \
--request POST \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/control-group/request
Sample Response
{
"data": {
"approved": false,
"request_path": "secret/foo",
"request_entity": {
"id": "c8b6e404-de4b-50a4-2917-715ff8beec8e",
"name": "Bob"
},
"authorizations": [
{
"entity_id": "6544a3ec-d3cd-443b-b87b-4fd2e889e0b7",
"entity_name": "Abby Jones"
},
{
"entity_id": "919084a4-417e-42ee-9d78-87fa2843af37",
"entity_name": "James Franklin"
}
]
}
}