f3df55ad58
* Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
35 lines
1.1 KiB
Plaintext
35 lines
1.1 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: secrets move - Command
|
|
description: |-
|
|
The "secrets move" command moves an existing secrets engine to a new path. All
|
|
leases from the old secrets engine are revoked, but all configurations
|
|
associated with the engine are preserved.
|
|
---
|
|
|
|
# secrets move
|
|
|
|
The `secrets move` command moves an existing secrets engine to a new path. Any
|
|
leases from the old secrets engine are revoked, but all configuration associated
|
|
with the engine is preserved. The command can be issued for a move within or across
|
|
namespaces, using namespace prefixes in the arguments.
|
|
|
|
The command will trigger a remount operation and uses the returned migration ID to poll the
|
|
status of the operation until a terminal state of `success` or `failure` is reached.
|
|
|
|
**Moving an existing secrets engine will revoke any leases from the old
|
|
engine.**
|
|
|
|
## Examples
|
|
|
|
Move the existing secrets engine at ns1/secret/ to ns2/kv/:
|
|
|
|
```shell-session
|
|
$ vault secrets move ns1/secret/ ns2/kv/
|
|
```
|
|
|
|
## Usage
|
|
|
|
There are no flags beyond the [standard set of flags](/vault/docs/commands)
|
|
included on all commands.
|