vault/website/content/api-docs/system/config-reload.mdx
Erica Thompson 0660ea6fac
Update README (#31244)
* Update README

Let contributors know that docs will now be located in UDR

* Add comments to each mdx doc

Comment has been added to all mdx docs that are not partials

* chore: added changelog

changelog check failure

* wip: removed changelog

* Fix content errors

* Doc spacing

* Update website/content/docs/deploy/kubernetes/vso/helm.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

---------

Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2025-07-22 08:12:22 -07:00

41 lines
1.7 KiB
Plaintext

---
layout: api
page_title: /sys/config/reload - HTTP API
description: The '/sys/config/reload' endpoint is used to reload specific parts of Vault's configuration.
---
> [!IMPORTANT]
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
# `/sys/config/reload`
@include 'alerts/restricted-root.mdx'
The `sys/config/reload` endpoint allows reloading specific parts of Vault's configuration.
Currently, it only supports reloading license information from files on disk.
| Method | Path |
| :----- | :---------------------------- |
| `POST` | `/sys/config/reload/:subsystem` |
### Parameters
- `subsystem` `(string: <required>)` - Specifies the subsystem for Vault to reload. This is part of the request URL.
## Reload license file <EnterpriseAlert product="vault" inline />
When the `:subsystem` URL parameter is specified as `license`, Vault re-reads
the license file if the license was provided using the `license_path` configuration
option or the `VAULT_LICENSE_PATH` environment variable. The updated license is
applied to Vault, and Vault will then enable/disable licensed features if the features
of the given license are different from those of the license Vault is currently using.
### Sample request
```shell-session
$ curl \
-X POST \
--header "X-Vault-Token: ..." \
'http://127.0.0.1:8200/v1/sys/config/reload/license'
```