Remount ( API )
The Remount documentation details the endpoints required to trigger and monitor the status of a remount operation.
Move backend
Restricted endpoint
The API path can only be called from the root or administrative namespace.The /sys/remount
endpoint moves an already-mounted backend to a new mount point. Remounting works for both secret
engines and auth methods.
Vault returns a migration ID when the remount operation completes. You can use the migration ID to look up the status of the mount migration. More details about the remount operation are described in Mount Migration.
Note: This endpoint requires a policy with both sudo
and update
capabilities to sys/remount
Note: A mount migration will revoke all leases for the secrets of a secrets backend or tokens of an auth backend, depending on which type of backend is being moved.
Method | Path |
---|---|
POST | /sys/remount |
Parameters
from
(string: <required>)
– Specifies the previous mount point.to
(string: <required>)
– Specifies the new destination mount point.
Sample payload ( cross namespace )
Sample payload ( cross namespace, auth mount )
Sample payload ( within namespace )
Sample request
Sample response
Monitor migration status
Restricted endpoint
The API path can only be called from the root or administrative namespace.This endpoint is used to monitor the status of a mount migration operation, using the ID returned in the response
of the sys/remount
call. The response contains the passed-in ID, the source and target mounts, and a status field
that displays in-progress
, success
or failure
.
Method | Path |
---|---|
GET | /sys/remount/status/:migration_id |
Parameters
migration_id
(string: <required>)
– Specifies the id of the mount migration
Sample request
Sample response