content large_string | url large_string | branch large_string | source large_string | embeddings list | score float64 |
|---|---|---|---|---|---|
# version-history The `version-history` command prints the historical list of installed Vault versions in chronological order. ```shell-session Note: Version tracking was added in 1.9.0. Earlier versions have not been tracked. The Build Date will only be available for versions 1.11.0 or greater. Version Installation Ti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/version-history.mdx | main | vault | [
0.04622362181544304,
0.04450191184878349,
-0.03675061836838722,
-0.060574889183044434,
0.08936590701341629,
-0.016719123348593712,
-0.04572033882141113,
-0.04631063714623451,
-0.0247426126152277,
0.01010274887084961,
0.06158163398504257,
0.007979393005371094,
0.017972487956285477,
-0.01939... | -0.068598 |
# namespace The `namespace` command groups subcommands for interacting with namespaces. ## Examples List all namespaces: ```shell-session $ vault namespace list ``` List all namespaces with additional details such as namespace ID and custom metadata: ```shell-session $ vault namespace list -detailed ``` Create a namesp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/namespace.mdx | main | vault | [
0.03845512121915817,
-0.03347599133849144,
-0.06922195106744766,
-0.00886617787182331,
-0.06428731977939606,
-0.05404118821024895,
0.04865429922938347,
-0.02801297977566719,
0.012942589819431305,
0.044798146933317184,
0.01667623594403267,
-0.09495916217565536,
0.05647178366780281,
0.018225... | -0.0011 |
# ssh The `ssh` command establishes an SSH connection with the target machine. This command uses one of the SSH secrets engines to authenticate and automatically establish an SSH connection to a host. This operation requires that the SSH secrets engine is mounted and configured. The user must have `ssh` installed local... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/ssh.mdx | main | vault | [
0.06851208209991455,
0.035059284418821335,
-0.02183213271200657,
-0.03952684625983238,
-0.07649561017751694,
-0.046427588909864426,
-0.024574952200055122,
0.018543066456913948,
-0.003500269493088126,
-0.03659734129905701,
-0.007008006796240807,
-0.07416392862796783,
0.08255475759506226,
0.... | -0.003153 |
# patch The `patch` command updates data in Vault at the given path (wrapper command for HTTP PATCH using the [JSON Patch format](https://datatracker.ietf.org/doc/html/rfc6902)). The data can be credentials, secrets, configuration, or arbitrary data. The specific behavior of the `patch` command is determined at the thi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/patch.mdx | main | vault | [
-0.051205284893512726,
0.028976062312722206,
-0.031242620199918747,
-0.01636902615427971,
-0.07470245659351349,
-0.09977829456329346,
0.003671931568533182,
0.002804327290505171,
-0.01907985657453537,
0.011756841093301773,
0.012939154170453548,
0.02160838432610035,
0.054910097271203995,
-0.... | 0.044485 |
# status The `status` command prints the current state of Vault including whether it is sealed and if HA mode is enabled. This command prints regardless of whether the Vault is sealed. The exit code reflects the seal status: - 0 - unsealed - 1 - error - 2 - sealed ## Examples Print the current Vault status: ```shell-se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/status.mdx | main | vault | [
0.07601071894168854,
0.051598720252513885,
-0.08034028112888336,
0.05746260657906532,
0.035361435264348984,
-0.05707978829741478,
0.01134837232530117,
0.0046572634018957615,
-0.007930655032396317,
0.012456306256353855,
0.08024493604898453,
-0.022086525335907936,
0.07309993356466293,
-0.006... | 0.051797 |
the storage or HA backend is raft. | | Raft Committed Index | The index of the committed log entry if the value is non-zero. | | Raft Applied Index | The highest index of raft log last applied to the finite state machine or added to `fsm\_pending` queue if the value is non-zero. | | Last WAL | Index of the last write-a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/status.mdx | main | vault | [
0.01154422014951706,
0.013025137595832348,
-0.11950543522834778,
0.09076734632253647,
0.03614387288689613,
-0.01978643611073494,
0.02440430223941803,
-0.026163289323449135,
-0.0012582446215674281,
0.07392603158950806,
-0.017385205253958702,
0.07910600304603577,
0.019050315022468567,
-0.118... | 0.157632 |
# read The `read` command reads data from Vault at the given path (wrapper command for HTTP GET). You can use the command to read secrets, generate dynamic credentials, get configuration details, and more. ## Examples Read entity details of a given ID: ```shell-session $ vault read identity/entity/id/2f09126d-d161-abb8... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/read.mdx | main | vault | [
-0.013240627944469452,
0.05434654653072357,
-0.08228128403425217,
-0.0025799390859901905,
-0.04909086599946022,
-0.023088891059160233,
-0.023415561765432358,
0.04875994101166725,
0.06685229390859604,
-0.0423242524266243,
-0.0013213041238486767,
-0.076626256108284,
0.07149999588727951,
-0.0... | -0.062306 |
# `monitor` Stream Vault server logs in real-time to `stdout`. ```shell-session $ vault monitor [flags] $ vault monitor [-help | -h] ``` ## Description `vault monitor` streams Vault server logs to `stdout` in real time based on the address stored in `VAULT\_ADDR` or passed through `-address`. Use the `-log-level` flag ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/monitor.mdx | main | vault | [
0.10261388123035431,
0.03693127632141113,
-0.12574972212314606,
-0.017777806147933006,
0.04525235667824745,
-0.09736368060112,
-0.010297609493136406,
-0.027971655130386353,
0.030309578403830528,
0.001865670783445239,
0.002969707129523158,
-0.039202749729156494,
0.04416076838970184,
0.05686... | -0.01712 |
# token capabilities The `token capabilities` command fetches the capabilities of a token for a given path. If you pass a token value as an argument, this command uses the `/sys/capabilities` endpoint and permission. In the absence of an explicit token value, this command uses the `/sys/capabilities-self` endpoint and ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/capabilities.mdx | main | vault | [
0.03769845515489578,
0.022275062277913094,
-0.07225523889064789,
0.018217401579022408,
0.003031558822840452,
-0.05819316953420639,
0.018293291330337524,
0.029737642034888268,
0.013826283626258373,
-0.015852168202400208,
0.00249662809073925,
-0.04689844325184822,
0.03269500285387039,
0.0672... | 0.080548 |
# token create The `token create` command creates a new token that can be used for authentication. This token will be created as a child of the currently authenticated token. The generated token will inherit all policies and permissions of the currently authenticated token unless you explicitly define a subset list pol... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/create.mdx | main | vault | [
-0.014955000951886177,
0.0016020826296880841,
-0.05278274044394493,
0.021343588829040527,
-0.021346043795347214,
-0.03960496932268143,
0.029819488525390625,
-0.01457326952368021,
0.05746991187334061,
-0.008997528813779354,
0.012966695241630077,
-0.002726844744756818,
0.04084015265107155,
0... | 0.061009 |
specified multiple times to attach multiple policies. - `-renewable` `(bool: true)` - Allow the token to be renewed up to it's maximum TTL. - `-role` `(string: "")` - Name of the role to create the token against. Specifying -role may override other arguments. The locally authenticated Vault token must have permission f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/create.mdx | main | vault | [
-0.026692286133766174,
0.0013809120282530785,
-0.05622955784201622,
-0.022853761911392212,
-0.050263695418834686,
-0.03471766784787178,
-0.0014999229460954666,
-0.0024421822745352983,
0.041821952909231186,
-0.030712265521287918,
0.03820064291357994,
0.017120346426963806,
0.09288906306028366,... | 0.012213 |
# token renew The `token renew` renews a token's lease, extending the amount of time it can be used. If a TOKEN is not provided, the locally authenticated token is used. Lease renewal will fail if the token is not renewable, the token has already been revoked, or if the token has already reached its maximum TTL. ## Exa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/renew.mdx | main | vault | [
0.038550470024347305,
0.05074723809957504,
-0.008414623327553272,
-0.04433711990714073,
-0.03672563657164574,
-0.020917627960443497,
-0.04370822012424469,
0.005488429684191942,
0.05465643107891083,
0.02055453509092331,
0.01885717548429966,
0.0037671211175620556,
0.030606340616941452,
0.017... | 0.061182 |
# token lookup The `token lookup` displays information about a token or accessor. If a TOKEN is not provided, the locally authenticated token is used. ## Examples Get information about the locally authenticated token (this uses the `/auth/token/lookup-self` endpoint and permission): ```shell-session $ vault token looku... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/lookup.mdx | main | vault | [
0.024325234815478325,
0.08874722570180893,
-0.11298616230487823,
-0.02733958140015602,
0.04015076905488968,
-0.07210057228803635,
0.015213669277727604,
-0.017057456076145172,
0.059957996010780334,
-0.04274790734052658,
-0.007058406714349985,
-0.004858541768044233,
-0.016037940979003906,
-0... | 0.046417 |
# token The `token` command groups subcommands for interacting with tokens. Users can create, lookup, renew, and revoke tokens. For more information on tokens, please see the [token concepts page](/vault/docs/concepts/tokens). ## Examples Create a new token: ```shell-session $ vault token create ``` Revoke a token: ```... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/index.mdx | main | vault | [
0.016760753467679024,
0.038744550198316574,
-0.053559914231300354,
0.024602415040135384,
-0.037374429404735565,
-0.05735741928219795,
0.024008234962821007,
0.007772990968078375,
0.03580835461616516,
-0.04766402393579483,
0.005635528359562159,
-0.011531644500792027,
0.05148668959736824,
-0.... | 0.092132 |
# token revoke The `token revoke` revokes authentication tokens and their children. If a TOKEN is not provided, the locally authenticated token is used. The `-mode` flag can be used to control the behavior of the revocation. ## Examples Revoke a token and all the token's children: ```shell-session $ vault token revoke ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/token/revoke.mdx | main | vault | [
0.0576336607336998,
0.11867070943117142,
-0.011868302710354328,
0.007684500887989998,
0.02630809135735035,
-0.04202647507190704,
0.04333222657442093,
-0.06533212214708328,
0.10861427336931229,
-0.018203217536211014,
0.04777522385120392,
0.020616166293621063,
0.027511348947882652,
-0.009290... | 0.024689 |
# kv enable-versioning The `kv enable-versioning` command turns on versioning for an existing non-versioned key/value secrets engine (KV version 1) at its path. ## Examples This command turns on versioning for the KV version 1 secrets engine enabled at "secret". ```shell-session $ vault kv enable-versioning secret Succ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/enable-versioning.mdx | main | vault | [
0.0587623305618763,
0.04710599035024643,
-0.09210028499364853,
-0.016235999763011932,
0.012057053856551647,
-0.0153170982375741,
-0.10582837462425232,
-0.022512013092637062,
-0.008861342445015907,
-0.01798277720808983,
0.049319278448820114,
-0.020693624392151833,
0.01271271426230669,
-0.01... | -0.06903 |
# kv list The `kv list` command returns a list of key names at the specified location. Folders are suffixed with /. The input must be a folder; list on a file will not return a value. Note that no policy-based filtering is performed on keys; do not encode sensitive information in key names. The values themselves are no... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/list.mdx | main | vault | [
0.01574048399925232,
0.05472694709897041,
-0.09033825248479843,
-0.02031930722296238,
0.022440534085035324,
-0.020549878478050232,
0.02732996828854084,
0.06411005556583405,
0.05171139910817146,
-0.01236248854547739,
0.09846800565719604,
-0.09812019020318985,
0.0818210244178772,
0.006232129... | -0.072077 |
# kv rollback ~> \*\*NOTE:\*\* This is a [KV version 2](/vault/docs/secrets/kv/kv-v2) secrets engine command, and not available for Version 1. The `kv rollback` command restores a given previous version to the current version at the given path. The value is written as a new version; for instance, if the current version... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/rollback.mdx | main | vault | [
-0.01896730624139309,
0.09200470894575119,
-0.04397149756550789,
-0.0036921771243214607,
0.02372949756681919,
-0.0031727831810712814,
-0.06685736030340195,
-0.031960684806108475,
0.04129067808389664,
-0.027093801647424698,
0.08767447620630264,
0.029258009046316147,
0.016705581918358803,
-0... | -0.079239 |
# kv metadata ~> \*\*NOTE:\*\* This is a [KV version 2](/vault/docs/secrets/kv/kv-v2) secrets engine command, and not available for Version 1. The `kv metadata` command has subcommands for interacting with the metadata and versions for the versioned secrets (KV version 2 secrets engine) at the specified path. ## Usage ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/metadata.mdx | main | vault | [
0.012198161333799362,
0.06867942214012146,
-0.07212789356708527,
-0.018933789804577827,
0.019444871693849564,
-0.01123471837490797,
-0.046104300767183304,
-0.0032325922511518,
0.037488047033548355,
-0.02432822622358799,
0.07012703269720078,
-0.07193378359079361,
0.03787365183234215,
-0.035... | -0.00323 |
configured max version is used. Once a key has more than the configured allowed versions the oldest version will be permanently deleted. - `-delete-version-after` `(string:"0s")` – Set the `delete-version-after` value to a duration to specify the `deletion\_time` for all new versions written to this key. If not set, th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/metadata.mdx | main | vault | [
0.040833115577697754,
0.03264446184039116,
-0.057003989815711975,
-0.062345754355192184,
0.013832447119057178,
-0.03773282840847969,
-0.07541771233081818,
-0.01830296218395233,
0.07481402903795242,
-0.037072934210300446,
0.05871891230344772,
0.046188805252313614,
0.051828533411026,
-0.0407... | -0.035334 |
# kv put The `kv put` command writes the data to the given path in the KV secrets engine. If working with KV v2, this command creates a new version of a secret at the specified location. If working with KV v1, this command stores the given secret at the specified location. Regardless of the KV version, if the value doe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/put.mdx | main | vault | [
0.013877786695957184,
0.05755267292261124,
-0.08704185485839844,
0.009043946862220764,
-0.0744515135884285,
0.007043683901429176,
-0.051765114068984985,
0.061349719762802124,
0.050465915352106094,
-0.021226847544312477,
0.0518135242164135,
-0.06150227412581444,
0.06210651993751526,
-0.0147... | -0.032805 |
# kv get The `kv get` command retrieves the value from KV secrets engine at the given key name. If no key exists with that name, an error is returned. If a key exists with the name but has no data, nothing is returned. ## Examples Retrieve the data of the key "creds": ```shell-session $ vault kv get -mount=secret creds... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/get.mdx | main | vault | [
0.0220661498606205,
0.123467355966568,
-0.053074099123477936,
0.0007545567932538688,
0.023445047438144684,
-0.020701171830296516,
-0.042480356991291046,
-0.01641407050192356,
0.08656115084886551,
-0.044016968458890915,
0.09233231842517853,
-0.10394908487796783,
0.03168535977602005,
-0.0435... | -0.067854 |
# kv The `kv` command groups subcommands for interacting with Vault's key/value secrets engine (both [KV version 1](/vault/docs/secrets/kv/kv-v1) and [KV Version 2](/vault/docs/secrets/kv/kv-v2). ## Syntax Option flags for a given subcommand are provided after the subcommand, but before the arguments. The path to where... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/index.mdx | main | vault | [
-0.034938711673021317,
0.05465575307607651,
-0.061098452657461166,
-0.01081814058125019,
-0.004329681862145662,
-0.03364182636141777,
-0.09412489086389542,
0.06033279746770859,
-0.017553232610225677,
-0.08417249470949173,
0.06287141144275665,
-0.09080041944980621,
0.04914126172661781,
0.04... | -0.090176 |
for a KV store get Retrieves data from the KV store list List data or secrets metadata Interact with Vault's Key-Value storage patch Sets or updates data in the KV store without overwriting put Sets or updates data in the KV store rollback Rolls back to a previous version of data undelete Undeletes versions in the KV s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/index.mdx | main | vault | [
-0.01705099269747734,
0.0499688982963562,
-0.039062466472387314,
0.021653052419424057,
-0.02462357096374035,
0.005422242917120457,
-0.05730924382805824,
-0.026428909972310066,
0.02771918475627899,
-0.03179844096302986,
0.09960010647773743,
0.034782033413648605,
0.010658533312380314,
-0.054... | -0.042243 |
# kv destroy ~> \*\*NOTE:\*\* This is a [KV version 2](/vault/docs/secrets/kv/kv-v2) secrets engine command, and not available for Version 1. The `kv destroy` command permanently removes the specified versions' data from the key/value secrets engine. If no key exists at the path, no action is taken. ## Examples Destroy... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/destroy.mdx | main | vault | [
0.023264283314347267,
0.09365007281303406,
-0.05517372861504555,
-0.03040631115436554,
0.03335997089743614,
-0.03293660283088684,
-0.05316709727048874,
-0.01504548080265522,
0.04153428599238396,
-0.002362031489610672,
0.044194430112838745,
-0.009592263028025627,
0.05044309422373772,
-0.004... | -0.05637 |
# kv undelete ~> \*\*NOTE:\*\* This is a [KV version 2](/vault/docs/secrets/kv/kv-v2) secrets engine command, and not available for Version 1. The `kv undelete` command undoes the deletes of the data for the provided version and path in the key-value store. This restores the data, allowing it to be returned on get requ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/undelete.mdx | main | vault | [
-0.017986426129937172,
0.07195157557725906,
-0.049948494881391525,
0.013489296659827232,
0.03144635260105133,
-0.02121547795832157,
-0.03402220830321312,
-0.02385057508945465,
0.05064958333969116,
-0.029711836948990822,
0.059562910348176956,
-0.026874855160713196,
0.04639767110347748,
-0.0... | -0.061249 |
# kv delete The `kv delete` command deletes the data for the provided path in the key/value secrets engine. If using KV version 2, its versioned data will not be fully removed, but marked as deleted and will no longer be returned in normal get requests. ## Examples Delete the latest version of the key "creds": ```shell... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/delete.mdx | main | vault | [
0.007946006953716278,
0.07624100893735886,
-0.04673659801483154,
-0.009589589200913906,
0.03494257479906082,
-0.024982893839478493,
-0.031920820474624634,
-0.04476159065961838,
0.0807894915342331,
-0.034178100526332855,
0.08088862895965576,
-0.027256732806563377,
0.05255969986319542,
-0.00... | -0.081865 |
# kv patch ~> \*\*NOTE:\*\* This is a [KV version 2](/vault/docs/secrets/kv/kv-v2) secrets engine command, and not available for Version 1. The `kv patch` command writes the data to the given path in the KV v2 secrets engine. The data can be of any type. Unlike the `kv put` command, the `patch` command combines the cha... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/kv/patch.mdx | main | vault | [
-0.004594366066157818,
0.06268700212240219,
-0.026984307914972305,
-0.013273798860609531,
-0.07603026926517487,
0.020275985822081566,
-0.03624183312058449,
0.03789889067411423,
0.0054294089786708355,
0.024248536676168442,
0.0877143144607544,
-0.058145780116319656,
0.05254611372947693,
-0.0... | -0.054322 |
# license inspect @include 'alerts/enterprise-only.mdx' The `license inspect` command describes the contents of a signed license string. ## Examples Describe license in the environment (either `VAULT\_LICENSE` for a raw value or `VAULT\_LICENSE\_PATH` for the path to a file containing the value): ```shell-session $ vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/license/inspect.mdx | main | vault | [
0.031137065961956978,
0.10129895806312561,
-0.06234651803970337,
-0.08670926839113235,
0.07325270771980286,
-0.014209314249455929,
0.06066548079252243,
-0.018470102921128273,
0.07142522931098938,
-0.012536407448351383,
-0.008034628815948963,
-0.007835286669433117,
0.02171270176768303,
-0.0... | 0.027581 |
# license get @include 'alerts/enterprise-only.mdx' The `license get` command reports on the license in use. With the `-signed` flag, it will return the actual license string, but only if the license is stored, as opposed to [autoloaded](/vault/docs/enterprise/license/autoloading). ## Examples Describe current license:... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/license/get.mdx | main | vault | [
0.02596418187022209,
0.06594853103160858,
-0.09516441076993942,
-0.06095418334007263,
0.04428136721253395,
0.045658815652132034,
0.07356421649456024,
0.012040315195918083,
0.03328721225261688,
-0.018213551491498947,
-0.0020817252807319164,
0.00453297421336174,
0.028743842616677284,
-0.0688... | -0.025401 |
# license @include 'alerts/enterprise-only.mdx' The `license` command groups subcommands for interacting with Vault licenses For more information, please see the [license documentation](/vault/docs/enterprise/license) ## Examples Query current license in use by a node: ```shell-session $ vault license get Key Value ---... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/license/index.mdx | main | vault | [
0.04493028298020363,
0.05714311823248863,
-0.09004288911819458,
-0.05030707269906998,
0.05255969613790512,
0.0066635506227612495,
0.045069992542266846,
-0.007803517859429121,
0.026683077216148376,
-0.005178332794457674,
-0.004105939995497465,
-0.02061784453690052,
0.05422946810722351,
-0.0... | 0.035936 |
# auth list The `auth list` command lists the auth methods enabled. The output lists the enabled auth methods and options for those methods. ## Deprecation status column As of 1.12, all built-in auth engines will have an associated Deprecation Status. This status will be reflected in the `Deprecation Status` column, se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/list.mdx | main | vault | [
-0.035167619585990906,
0.00033841660479083657,
-0.030616138130426407,
-0.01973145082592964,
0.05561891570687294,
-0.017725585028529167,
-0.05232178419828415,
-0.06807056814432144,
0.0007223350694403052,
-0.053386181592941284,
0.07512039691209793,
0.03955506533384323,
-0.03950665518641472,
... | 0.099404 |
# auth disable The `auth disable` command disables an auth method at a given path, if one exists. This command is idempotent, meaning it succeeds even if no auth method is enabled at the path. Once an auth method is disabled, it can no longer be used for authentication. \*\*All access tokens generated via the disabled ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/disable.mdx | main | vault | [
0.030563155189156532,
0.1180863082408905,
-0.08266256749629974,
0.00552055798470974,
0.015320123173296452,
-0.033360596746206284,
0.01256971899420023,
-0.07304783910512924,
0.029158931225538254,
-0.032491642981767654,
0.014905478805303574,
0.050933293998241425,
0.06785119324922562,
0.00971... | 0.033918 |
# auth move The `auth move` command moves an existing auth method to a new path. Any leases from the old auth method 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 t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/move.mdx | main | vault | [
0.019083425402641296,
-0.016625408083200455,
-0.06648636609315872,
-0.011919762939214706,
-0.009085397236049175,
-0.05091514810919762,
0.044809918850660324,
-0.05296841636300087,
0.016467483714222908,
0.043438028544187546,
0.07029511779546738,
-0.04403402656316757,
0.07318951189517975,
0.0... | 0.012912 |
# auth The `auth` command groups subcommands for interacting with Vault's auth methods. Users can list, enable, disable, and get help for different auth methods. For more information, please see the [auth method documentation](/vault/docs/auth) or the [authentication concepts](/vault/docs/concepts/auth) page. To authen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/index.mdx | main | vault | [
0.06058387830853462,
0.03794824704527855,
-0.08092014491558075,
-0.00681812409311533,
-0.032502174377441406,
-0.04067210480570793,
-0.00047316355630755424,
0.007351062260568142,
0.01205525454133749,
-0.03231049329042435,
-0.005961691495031118,
-0.01427840068936348,
0.04561826214194298,
0.0... | -0.031022 |
# auth enable The `auth enable` command enables an auth method at a given path. If an auth method already exists at the given path, an error is returned. After the auth method is enabled, it usually needs configuration. The configuration varies by auth method. An auth method is responsible for authenticating users or m... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/enable.mdx | main | vault | [
0.06612559407949448,
0.03275882080197334,
-0.11766906082630157,
-0.015253780409693718,
-0.028783496469259262,
-0.027078397572040558,
0.02845189906656742,
0.006715564057230949,
0.018383260816335678,
-0.01119923498481512,
0.008450889028608799,
0.020521536469459534,
0.057264454662799835,
0.00... | -0.004949 |
Configures the semantic version of the plugin to use. If unspecified, implies the built-in or any matching unversioned plugin that may have been registered. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/enable.mdx | main | vault | [
-0.02245153859257698,
-0.08983433991670609,
-0.05108856409788132,
-0.015205832198262215,
0.02719893306493759,
0.01845528557896614,
-0.046124450862407684,
-0.06510122865438461,
-0.010972184129059315,
-0.025083942338824272,
0.08740857243537903,
-0.008520293049514294,
-0.060820601880550385,
0... | 0.118195 |
# auth tune The `auth tune` command tunes the configuration options for the auth method at the given PATH. The argument corresponds to the \*\*path\*\* where the auth method is enabled, not the auth \*\*type\*\*. ## Examples Before tuning the auth method configuration, view the current configuration of the auth method ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/tune.mdx | main | vault | [
0.08598014712333679,
0.026126274839043617,
-0.09866413474082947,
-0.007228226866573095,
-0.03380848839879036,
-0.07067623734474182,
-0.0043700686655938625,
-0.019322147592902184,
-0.003468866227194667,
0.007824624888598919,
-0.008484120480716228,
0.012265265919268131,
0.086520716547966,
0.... | 0.000909 |
`-passthrough-request-headers` `(string: "")` - request header values that will be sent to the auth method. Note that multiple keys may be specified by providing this option multiple times, each time with 1 key. - `-token-type` `(string: "")` - Specifies the type of tokens that should be returned by the auth method. - ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/tune.mdx | main | vault | [
-0.008513652719557285,
0.019309839233756065,
-0.04229823127388954,
-0.0037002034951001406,
-0.007717522792518139,
-0.01937243714928627,
-0.038245100528001785,
0.003260386176407337,
0.029961595311760902,
-0.029774773865938187,
0.033565081655979156,
0.0009528747759759426,
0.03614088520407677,
... | -0.046428 |
# auth help The `auth help` command prints usage and help for an auth method. - If given a TYPE, this command prints the default help for the auth method of that type. - If given a PATH, this command prints the help output for the auth method enabled at that path. This path must already exist. Each auth method produces... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/auth/help.mdx | main | vault | [
0.06687112897634506,
0.07862435281276703,
-0.08138691633939743,
-0.007477640174329281,
0.030720051378011703,
-0.04312433674931526,
0.03808164969086647,
-0.001719730906188488,
-0.014183517545461655,
-0.055203650146722794,
0.016667740419507027,
-0.002320864936336875,
0.018027814105153084,
0.... | -0.016198 |
# secrets list The `secrets list` command lists the enabled secrets engines on the Vault server. This command also outputs information about the enabled path including configured TTLs and human-friendly descriptions. A TTL of "system" indicates that the system default is in use. ## Deprecation status column As of 1.12,... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/list.mdx | main | vault | [
-0.03787915036082268,
0.006441861856728792,
-0.018176360055804253,
-0.014712982811033726,
0.0369412787258625,
-0.033616408705711365,
-0.07917018979787827,
-0.0461123026907444,
0.038989849388599396,
-0.06199605017900467,
0.05679741129279137,
0.06466571986675262,
-0.02428067848086357,
-0.064... | 0.062076 |
# secrets disable The `secrets disable` command disables an secrets engine at a given PATH. The argument corresponds to the enabled PATH of the engine, not the TYPE! All secrets created by this engine are revoked and its Vault data is removed. When a secrets engine is disabled, \*\*all secrets generated via the secrets... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/disable.mdx | main | vault | [
-0.027252722531557083,
0.10643181949853897,
-0.0042891548946499825,
0.0494854673743248,
0.030162887647747993,
-0.02590687945485115,
-0.05000264197587967,
-0.0645657405257225,
0.06853821128606796,
0.002273113466799259,
0.04041160270571709,
0.07602566480636597,
0.036817699670791626,
-0.01937... | -0.025119 |
# 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 co... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/move.mdx | main | vault | [
-0.026665961369872093,
-0.026639573276042938,
-0.052804406732320786,
-0.01593991555273533,
0.0026489244773983955,
-0.017522981390357018,
-0.013611000031232834,
-0.07902639359235764,
0.04211850464344025,
0.011779326014220715,
0.07233545929193497,
-0.008076624944806099,
0.014040747657418251,
... | 0.048948 |
# secrets The `secrets` command groups subcommands for interacting with Vault's secrets engines. Each secrets engine behaves differently. Please see the documentation for more information. Some secrets engines persist data, some act as data pass-through, and some generate dynamic credentials. The secrets engine will li... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/index.mdx | main | vault | [
0.017063837498426437,
-0.03089502453804016,
-0.10486987978219986,
0.0386221818625927,
-0.054963111877441406,
-0.019973985850811005,
-0.053500592708587646,
0.00851673074066639,
0.04409099742770195,
-0.02384124882519245,
0.021975446492433548,
0.0219290591776371,
0.05209936201572418,
-0.02853... | -0.0351 |
# secrets enable The `secrets enable` command enables a secrets engine at a given path. If a secrets engine already exists at the given path, an error is returned. After the secrets engine is enabled, it usually needs configuration. The configuration varies by secrets engine. By default, secrets engines are enabled at ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/enable.mdx | main | vault | [
0.0167407039552927,
-0.02389432117342949,
-0.08157140761613846,
0.03551342338323593,
-0.017232947051525116,
0.024566037580370903,
-0.06430575996637344,
-0.006553493905812502,
0.03416011109948158,
-0.023517277091741562,
0.01463793870061636,
0.01799277774989605,
0.039936721324920654,
-0.0038... | -0.042183 |
time with 1 key. - `-allowed-managed-keys` `(string: "")` - Managed key name(s) that the mount in question is allowed to access. Note that multiple keys may be specified by providing this option multiple times, each time with 1 key. - `-delegated-auth-accessors` `(string: "")` - An authorized accessor the auth backend ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/enable.mdx | main | vault | [
-0.006788681726902723,
-0.006470326334238052,
-0.07158924639225006,
0.009127039462327957,
-0.04270542412996292,
-0.09006299823522568,
-0.017797334119677544,
-0.02162960171699524,
0.04885535687208176,
-0.005283770151436329,
0.06768803298473358,
-0.004515809006989002,
0.07600068300962448,
0.... | -0.040279 |
# secrets tune The `secrets tune` command tunes the configuration options for the secrets engine at the given PATH. The argument corresponds to the PATH where the secrets engine is enabled, not the type. ## Examples Before tuning the secret mount, view the current configuration of the mount enabled at "pki/": ```shell-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/tune.mdx | main | vault | [
0.019698547199368477,
0.06508971005678177,
-0.058832984417676926,
-0.0015395311638712883,
-0.024569712579250336,
-0.05857590585947037,
0.030107662081718445,
-0.029712669551372528,
0.017200656235218048,
-0.0501607321202755,
0.030843054875731468,
0.012813197448849678,
0.045378848910331726,
0... | -0.030997 |
- `-plugin-version` `(string: "")` - Configures the semantic version of the plugin to use. The new version will not start running until the mount is [reloaded](/vault/docs/commands/plugin/reload). | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/secrets/tune.mdx | main | vault | [
0.031550899147987366,
-0.047230057418346405,
0.013087838888168335,
-0.03554042428731918,
0.0017223183531314135,
-0.024633727967739105,
-0.09345957636833191,
-0.042036477476358414,
0.001881587551906705,
-0.039616599678993225,
0.07552915811538696,
0.03721427917480469,
-0.03742007166147232,
0... | -0.083433 |
# plugin list The `plugin list` command lists all available plugins in the plugin catalog. It can be used alone or with a type such as "auth", "database", or "secret". ## Deprecation status column As of 1.12, all builtin plugins will have an associated Deprecation Status. This status will be reflected in the `Deprecati... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/list.mdx | main | vault | [
0.017648180946707726,
0.010919777676463127,
-0.04397716745734215,
-0.027095621451735497,
-0.001773189869709313,
0.0048443712294101715,
-0.043062832206487656,
-0.03450788930058479,
-0.00009601475903764367,
0.02630423940718174,
0.05310187488794327,
-0.04210402071475983,
-0.02795790322124958,
... | 0.045609 |
# plugin register The `plugin register` command registers a new plugin in Vault's plugin catalog. The plugin's type of "auth", "database", or "secret" must be included. To register an enterprise plugin, you must register with the extracted `.zip` file, not the binary. Refer to the [Enterprise plugins](/vault/docs/plugi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/register.mdx | main | vault | [
0.02721928060054779,
-0.08614962548017502,
-0.09282705187797546,
-0.03519207239151001,
-0.06042484566569328,
0.001735724974423647,
-0.021002864465117455,
0.02384686842560768,
0.022135738283395767,
0.01552996039390564,
0.04021031782031059,
-0.05174883082509041,
-0.013073981739580631,
0.0484... | -0.015301 |
secret and auth plugins with artifacts containing `metadata.json` and `metadata.json.sig`. To use automatic downloads, your network must permit HTTPS and TCP port 443 between all Vault cluster nodes and `releases.hashicorp.com`. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/register.mdx | main | vault | [
0.02174030803143978,
0.027986377477645874,
-0.08173943310976028,
-0.02698122337460518,
0.010268357582390308,
-0.05126781761646271,
-0.056465886533260345,
-0.03395751863718033,
0.037045132368803024,
-0.008595788851380348,
0.07188169658184052,
0.008102661930024624,
0.004142160061746836,
0.01... | 0.069498 |
# plugin The `plugin` command groups subcommands for interacting with Vault's plugins and the plugin catalog ## Examples List all available secret plugins in the catalog: ```shell-session $ vault plugin list secret Name Version ---- ------- ad v0.14.0+builtin alicloud v0.13.0+builtin ... ``` Register a new secret plugi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/index.mdx | main | vault | [
-0.03544437140226364,
-0.025811193510890007,
-0.05575045570731163,
0.00493953051045537,
-0.00010328119242331013,
-0.005225320812314749,
0.03424907848238945,
-0.03275280445814133,
0.02597203478217125,
0.0006976944277994335,
0.07909119874238968,
-0.0920020341873169,
-0.005202499683946371,
0.... | -0.009267 |
# plugin info The `plugin info` displays information about a plugin in the catalog. The plugin's type of "auth", "database", or "secret" must be included. ## deprecation\_status field As of 1.12, all builtin plugins will have an associated Deprecation Status. This status will be reflected in the `deprecation\_status` k... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/info.mdx | main | vault | [
0.02932380884885788,
0.04639643803238869,
-0.05186214670538902,
-0.037016186863183975,
-0.018254203721880913,
-0.034288372844457626,
0.004938572645187378,
-0.0032179420813918114,
0.027187403291463852,
-0.0027346170973032713,
0.055970776826143265,
-0.027952447533607483,
-0.004055807366967201,... | -0.029779 |
# plugin reload The `plugin reload` command is used to reload mounted plugin backends. Either the plugin name (`plugin`) or the desired plugin backend mounts (`mounts`) must be provided, but not both. In the case that the plugin name is provided, all mounted paths that use that plugin backend will be reloaded. If run w... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/reload.mdx | main | vault | [
0.026061298325657845,
-0.06447809934616089,
-0.015696443617343903,
0.0204461757093668,
-0.03794048726558685,
-0.039065614342689514,
-0.00011995012027909979,
-0.045513130724430084,
0.03363059088587761,
-0.029453394934535027,
0.0401742048561573,
0.0024614788126200438,
0.04974217712879181,
0.... | -0.061467 |
# plugin deregister The `plugin deregister` command deregisters an existing plugin from Vault's plugin catalog. If the plugin does not exist, no error is returned. The plugin's type of "auth", "database", or "secret" must be included. ## Examples Deregister a plugin: ```shell-session $ vault plugin deregister auth my-c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/deregister.mdx | main | vault | [
-0.0021433967631310225,
0.021709095686674118,
-0.03151420131325722,
-0.007841038517653942,
-0.010582216084003448,
-0.03082449361681938,
-0.008240066468715668,
-0.04104810953140259,
-0.01423606462776661,
-0.012551181949675083,
0.07013953477144241,
-0.06404009461402893,
-0.008633404970169067,
... | -0.024002 |
# plugin list List all plugin runtimes currently registered with Vault. Returns all the available plugin runtimes or an error if the set of registered runtimes is empty. Vault considers any registered plugin runtime "available", regardless of whether it is currently in use. ## Examples List all available plugin runtime... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/runtime/list.mdx | main | vault | [
0.03843478113412857,
-0.010568873025476933,
-0.1081746369600296,
0.010394178330898285,
0.03471897169947624,
-0.03696107491850853,
-0.018391193822026253,
0.011831827461719513,
0.018539411947131157,
-0.02730714902281761,
0.05299755185842514,
-0.07383899390697479,
-0.018301155418157578,
0.029... | 0.009054 |
# plugin runtime register Register a new plugin runtime in the plugin runtime catalog of your Vault instance. Support for runtime types is currently limited to `container`. To use a registered plugin runtime, use the `-runtime` option with the [plugin registration command](/vault/docs/commands/plugin/register). ## Exam... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/runtime/register.mdx | main | vault | [
0.030827045440673828,
0.0016429130919277668,
-0.1031830757856369,
0.01629931665956974,
-0.01562972366809845,
-0.05937438830733299,
-0.025191722437739372,
0.0369926318526268,
-0.022019391879439354,
-0.014812477864325047,
0.0022193321492522955,
-0.05373996123671532,
-0.013588877394795418,
0.... | 0.005246 |
# plugin runtime The `plugin runtime` command groups subcommands for interacting with and configuring the context within which your external plugins run. Support for runtime types is currently limited to `container`. Support for the 'container` runtime is currently limited to Linux. If you register a container plugin w... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/runtime/index.mdx | main | vault | [
-0.001181751023977995,
-0.05441270023584366,
-0.09167199581861496,
0.00620051147416234,
0.024904577061533928,
-0.09985972940921783,
-0.03317844867706299,
0.06795996427536011,
-0.010628041811287403,
-0.04091700538992882,
0.02144554816186428,
-0.0491810068488121,
0.006075568962842226,
0.0387... | 0.012513 |
# plugin runtime info Displays information about a plugin runtime in the catalog with the given name. If the plugin runtime does not exist, an error is returned. Support for runtime types is currently limited to `container`. ## Examples Display information about a plugin ```shell-session $ vault plugin runtime info -ty... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/runtime/info.mdx | main | vault | [
0.05005083233118057,
0.02770891785621643,
-0.11071014404296875,
0.026551932096481323,
0.01205112598836422,
-0.0613519512116909,
-0.00853430014103651,
0.03203655779361725,
0.0024342744145542383,
-0.023907389491796494,
0.025090597569942474,
-0.06302361935377121,
-0.000013006140761717688,
-0.... | 0.006523 |
# plugin runtime deregister Deregister an existing plugin runtime in the catalog with the given name. Returns an error if a registered plugin references the named plugin runtime or the named runtime does not exist. Support for runtime types is currently limited to `container`. ## Examples Deregister a plugin: ```shell-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/plugin/runtime/deregister.mdx | main | vault | [
-0.017580077052116394,
-0.002141187898814678,
-0.021037381142377853,
0.035390883684158325,
0.014468074776232243,
-0.049550727009773254,
0.002724671270698309,
0.01200008112937212,
-0.025219419971108437,
-0.042407143861055374,
0.02945786528289318,
-0.08099815994501114,
-0.05359508469700813,
... | 0.028459 |
# `vault agent` Start an instance of Vault Agent. ```shell-session $ vault agent -config $ vault agent [-help | -h] ``` ## Description `vault agent` start an instance of Vault Agent, which automatically authenticates and fetches secrets for client applications. \*\*None\*\* ## Command arguments None. ## Command options... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/agent/index.mdx | main | vault | [
0.050661683082580566,
0.046361204236745834,
-0.118658147752285,
-0.09261579066514969,
-0.012097735889256,
-0.035793058574199677,
0.018729396164417267,
0.02106235921382904,
0.024091830477118492,
-0.012540709227323532,
0.028945276513695717,
-0.01664695329964161,
0.1072293147444725,
0.0485072... | -0.04649 |
# `agent generate-config` Use secrets plugin data to generate a basic [configuration file](/vault/docs/agent-and-proxy/agent#configuration-file-options) for running Vault Agent in [process supervisor mode](/vault/docs/agent-and-proxy/agent/process-supervisor). ```shell-session $ vault agent generate-config -type [optio... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/agent/generate-config.mdx | main | vault | [
-0.002177274553105235,
0.03860151395201683,
-0.11570680141448975,
-0.015132870525121689,
-0.027362337335944176,
-0.03029821813106537,
-0.02529996819794178,
0.013966355472803116,
-0.047932401299476624,
-0.021967735141515732,
0.03244028612971306,
-0.025697173550724983,
0.05575926974415779,
0... | 0.037087 |
# lease renew The `lease renew` command renews the lease on a secret, extending the time that it can be used before it is revoked by Vault. Every secret in Vault has a lease associated with it. If the owner of the secret wants to use it longer than the lease, then it must be renewed. Renewing the lease does not change ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/lease/renew.mdx | main | vault | [
-0.009386890567839146,
0.04698684439063072,
-0.050198063254356384,
-0.002837786916643381,
-0.014878775924444199,
-0.0034240051172673702,
-0.04151124879717827,
-0.027120117098093033,
0.0466993972659111,
0.02368728257715702,
0.07864443957805634,
0.05311422795057297,
0.008803458884358406,
0.0... | -0.024209 |
# lease lookup The `lease lookup` command retrieves information on the lease of a secret. Every secret in Vault has a lease associated with it. Users can look up information on the lease by referencing the lease ID. ## Examples Lookup a lease: ```shell-session $ vault lease lookup database/creds/readonly/27e1b9a1-27b8-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/lease/lookup.mdx | main | vault | [
-0.0023992895148694515,
0.08773203194141388,
-0.11859458684921265,
-0.0072731804102659225,
0.04175451770424843,
-0.027033431455492973,
-0.0004747269849758595,
-0.046504318714141846,
0.06974669545888901,
-0.0028468549717217684,
0.0702771544456482,
0.006712521426379681,
0.0020670918747782707,
... | 0.005654 |
# lease The `lease` command groups subcommands for interacting with leases attached to secrets. For leases attached to tokens, use the [`vault token`](/vault/docs/commands/token) subcommand. ## Examples Lookup a lease: ```shell-session $ vault lease lookup database/creds/readonly/27e1b9a1-27b8-83d9-9fe0-d99d786bdc83 Ke... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/lease/index.mdx | main | vault | [
0.01913612149655819,
0.04228386655449867,
-0.04870149865746498,
-0.003664227668195963,
-0.04906989261507988,
-0.026212148368358612,
-0.03259113430976868,
0.0036223172210156918,
0.059166762977838516,
0.01155140995979309,
0.03424231335520744,
-0.008215194568037987,
0.05024635046720505,
0.017... | -0.011286 |
# lease revoke The `lease revoke` command revokes the lease on a secret, invalidating the underlying secret. ## Examples Revoke a lease: ```shell-session $ vault lease revoke database/creds/readonly/27e1b9a1-27b8-83d9-9fe0-d99d786bdc83 Success! Revoked lease: database/creds/readonly/27e1b9a1-27b8-83d9-9fe0-d99d786bdc83... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/lease/revoke.mdx | main | vault | [
0.00018682412337511778,
0.07000498473644257,
-0.005977995693683624,
0.02018529176712036,
-0.017735948786139488,
-0.024044007062911987,
-0.015322682447731495,
-0.07422585040330887,
0.0682092234492302,
0.01247550267726183,
0.05741716921329498,
0.05984491482377052,
0.052071988582611084,
0.045... | -0.039755 |
# transit The `transit` command groups subcommands for interacting with Vault's [Transit Secrets Engine](/vault/docs/secrets/transit). ## Syntax Option flags for a given subcommand are provided after the subcommand, but before the arguments. ## Examples To [import](/vault/docs/commands/transit/import) keys into a mount... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/transit/index.mdx | main | vault | [
0.019690033048391342,
-0.011096692644059658,
-0.026290856301784515,
0.04316626489162445,
-0.01554802618920803,
-0.069872185587883,
-0.00929941888898611,
0.0001177291851490736,
-0.02817702479660511,
-0.015667380765080452,
0.052286840975284576,
-0.018758879974484444,
0.08852259069681168,
0.0... | 0.010052 |
# transit import and transit import-version The `transit import` and `transit import-version` commands import the specified key into Transit, via the [Transit BYOK mechanism](/vault/docs/secrets/transit#bring-your-own-key-byok). The former imports this key as a new key, failing if it already exists, whereas the latter ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/transit/import.mdx | main | vault | [
0.03540794923901558,
-0.03909936174750328,
-0.01160257775336504,
0.034450333565473557,
0.007229508366435766,
-0.052019041031599045,
-0.04025048762559891,
-0.009550217539072037,
0.001936436165124178,
0.02147727645933628,
0.04016653448343277,
0.020361363887786865,
0.07656921446323395,
-0.006... | -0.005886 |
# `audit list` List information about active audit devices. ```shell-session $ vault audit list [flags] $ vault audit list [-help | -h] ``` ## Description `vault audit list` displays information about active audit devices. ListAuditDevices - [`GET:/sys/audit`](/vault/api-docs/system/audit#list-enabled-audit-devices) ##... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/audit/list.mdx | main | vault | [
0.08035138994455338,
0.07401658594608307,
-0.10752847790718079,
-0.04340251535177231,
0.06700744479894638,
-0.03236909210681915,
0.08464738726615906,
-0.021263116970658302,
-0.013070916756987572,
0.015325701795518398,
0.035294193774461746,
-0.022706808522343636,
0.04958416521549225,
-0.000... | 0.008643 |
# `audit disable` Disable an audit device if it exists. ```shell-session $ vault audit disable [flags] $ vault audit disable [-help | -h] ``` ## Description `vault audit disable` deactivates an audit device without destroying data already logged by the device. The operation is idempotent and succeeds if the audit devic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/audit/disable.mdx | main | vault | [
0.04028727859258652,
0.08579707890748978,
-0.03841252997517586,
-0.02682916261255741,
0.06749384105205536,
-0.0682729184627533,
0.03341706097126007,
-0.08390257507562637,
0.04608051851391792,
-0.009007587097585201,
0.06187133863568306,
0.02057671546936035,
0.06798761337995529,
0.0603346563... | -0.041677 |
# `audit enable` Enable a new audit device. ```shell-session $ vault audit enable [flags] [options] [...] $ vault audit enable [-help | -h] ``` ## Description `audit enable` creates and enables an audit device at the given path or returns an error if an audit device already exists at the given path. The device configur... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/audit/enable.mdx | main | vault | [
0.07160872220993042,
0.028774606063961983,
-0.06370123475790024,
-0.03884357213973999,
0.03792829439043999,
-0.05471831560134888,
0.042390767484903336,
-0.033994436264038086,
0.034391529858112335,
-0.013185199350118637,
0.052050910890102386,
-0.03705763816833496,
0.04566157981753349,
0.061... | -0.02138 |
# `hcp connect` Authenticate users or machines to HCP then cache the connection token and address locally. ```shell-session $ vault hcp connect [options] $ vault hcp connect [-help | -h] ``` ## Description Use `hcp connect` to authenticate with explicit credentials or interactive browser login. By default, `hcp connect... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/hcp/connect.mdx | main | vault | [
0.053717490285634995,
0.042694710195064545,
-0.05400397256016731,
-0.07449548691511154,
-0.046639587730169296,
0.010684502311050892,
-0.019156184047460556,
-0.023085176944732666,
0.02687661536037922,
-0.053110528737306595,
0.013620095327496529,
-0.05159522220492363,
0.08251335471868515,
-0... | -0.012126 |
# transform The `transform` command groups subcommands for interacting with Vault's [Transform Secrets Engine](/vault/docs/secrets/transform). ## Syntax Option flags for a given subcommand are provided after the subcommand, but before the arguments. ## Examples To [import](/vault/docs/commands/transform/import) keys in... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/transform/index.mdx | main | vault | [
-0.03081580065190792,
0.06002092361450195,
-0.07647939771413803,
0.01890331320464611,
-0.022560711950063705,
-0.06522627919912338,
-0.020455332472920418,
0.06181946024298668,
-0.011007665656507015,
-0.03023952804505825,
0.04474152252078056,
-0.0025349094066768885,
0.0704120397567749,
0.005... | -0.006451 |
# transform import and transform import-version The `transform import` and `transform import-version` commands import the specified key into Transform, via the [Transform BYOK mechanism](/vault/docs/secrets/transform#bring-your-own-key-byok). The former imports this key as a new key, failing if it already exists, where... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/transform/import.mdx | main | vault | [
-0.015959231182932854,
0.025051666423678398,
-0.06328626722097397,
0.006006959825754166,
-0.0010791734093800187,
-0.04325167462229729,
-0.04363417625427246,
0.027291418984532356,
0.013577708974480629,
0.009956051595509052,
0.04240710660815239,
0.0415475107729435,
0.06365553289651871,
-0.00... | -0.020936 |
# operator key-status The `operator key-status` provides information about the active encryption key. Specifically, the current key term and the key installation time. ## Examples Get the key status: ```shell-session $ vault operator key-status Key Term 2 Install Time 01 Jan 17 12:30 UTC Encryption Count 4494 ``` ## Us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/key-status.mdx | main | vault | [
0.08196843415498734,
0.04415154084563255,
-0.12410563975572586,
-0.009716375730931759,
-0.007455175276845694,
-0.04962214455008507,
0.00966583751142025,
0.00446911109611392,
0.0313703678548336,
0.009861558675765991,
0.030070152133703232,
0.02658092975616455,
0.05974666401743889,
-0.0210218... | -0.015422 |
# operator migrate The `operator migrate` command copies data between storage backends to facilitate migrating Vault between configurations. It operates directly at the storage level, with no decryption involved. Keys in the destination storage backend will be overwritten, and the destination should \_not\_ be initiali... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/migrate.mdx | main | vault | [
0.03018452599644661,
-0.0012112798867747188,
-0.04124855622649193,
-0.03694432973861694,
0.015288316644728184,
-0.05250628665089607,
-0.028228048235177994,
-0.054811425507068634,
0.032379962503910065,
-0.024846840649843216,
0.06848281621932983,
-0.0031165163964033127,
0.05694292485713959,
... | -0.045941 |
Only keys at or after this value will be copied. - `-reset` - Reset the migration lock. A lock file is added during migration to prevent starting the Vault server or another migration. The `-reset` option can be used to remove a stale lock file if present. - `-max-parallel` `int: 10` - Allows the operator to specify th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/migrate.mdx | main | vault | [
-0.017973177134990692,
-0.03947480022907257,
-0.11401290446519852,
-0.05563667416572571,
-0.033192094415426254,
-0.0401485413312912,
-0.029281336814165115,
-0.038647279143333435,
0.0269479900598526,
-0.0071535417810082436,
0.1327274888753891,
0.06184916943311691,
0.03600325062870979,
-0.10... | 0.014301 |
# operator members The `operator members` lists the active node and the peers that it's heard from since it became active. ## Examples Get the key status: ```shell-session $ vault operator members Host Name API Address Cluster Address Active Node Version Upgrade Version Redundancy Zone Last Echo --------- ----------- -... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/members.mdx | main | vault | [
0.023844456300139427,
0.0221673883497715,
-0.032315000891685486,
-0.007365756202489138,
0.025957558304071426,
-0.055011823773384094,
0.009417959488928318,
-0.10762693732976913,
0.01513310894370079,
0.003191129770129919,
0.026384055614471436,
-0.02519579418003559,
0.051704224199056625,
-0.0... | 0.086569 |
# operator rotate The `operator rotate` command rotates the underlying encryption key, which secures data written to storage. This installs a new key in the key ring. This new key encrypts new data, while older keys in the ring decrypt older data. This is an online operation and does not cause downtime. This command ru... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/rotate.mdx | main | vault | [
0.014713158831000328,
0.045805979520082474,
-0.08914405107498169,
-0.03462646156549454,
-0.08618825674057007,
-0.03924701735377312,
-0.007756896782666445,
-0.001163645414635539,
0.07391534745693207,
0.003109169425442815,
0.08707054704427719,
0.13049937784671783,
0.08917795121669769,
-0.036... | -0.015495 |
# operator generate-root The `operator generate-root` command generates a new root token by combining a quorum of share holders. With the `-dr-token` or `-recovery-token` options, it can generate a DR operation token or a recovery token in the same way. One of the following must be provided to start the root token gene... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/generate-root.mdx | main | vault | [
-0.05444181710481644,
0.020826030522584915,
-0.06730912625789642,
0.024687571451067924,
-0.06599937379360199,
-0.04300707206130028,
0.0003874970425385982,
0.05468958243727684,
0.015090997330844402,
-0.009337077848613262,
-0.01048287097364664,
0.018538495525717735,
0.04925696179270744,
-0.0... | -0.01209 |
# operator unseal The `operator unseal` allows the user to provide a portion of the root key to unseal a Vault server. Vault starts in a sealed state. It cannot perform operations until it is unsealed. This command accepts a portion of the master key (an "unseal key"). The unseal key can be supplied as an argument to t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/unseal.mdx | main | vault | [
0.03249730169773102,
0.07952554523944855,
-0.0535409189760685,
0.007930244319140911,
-0.03690481558442116,
-0.01920534484088421,
-0.025333376601338387,
-0.006949223577976227,
0.026524601504206657,
0.002460508607327938,
0.0007680793642066419,
-0.05367576330900192,
0.037311866879463196,
-0.0... | -0.021774 |
# operator The `operator` command groups subcommands for operators interacting with Vault. Most users will not need to interact with these commands. ## Examples Initialize a new Vault cluster: ```shell-session $ vault operator init Unseal Key 1: sP/4C/fwIDjJmHEC2bi/1Pa43uKhsUQMmiB31GRzFc0R Unseal Key 2: kHkw2xTBelbDFIM... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/index.mdx | main | vault | [
0.030390240252017975,
-0.0027899560518562794,
-0.062218599021434784,
0.003986877854913473,
-0.047025468200445175,
-0.04878511279821396,
-0.029177537187933922,
-0.015869200229644775,
0.026733340695500374,
-0.025573929771780968,
0.014455454424023628,
-0.03885050117969513,
0.053788360208272934,... | 0.045876 |
# operator utilization The `operator utilization` allows the Vault Enterprise users to generate license utilization reporting bundles. When users have disabled automated license reporting, use this command to manually generate the report and send it to HashiCorp. Refer to the [manual license utilization reporting](/vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/utilization.mdx | main | vault | [
0.05489674583077431,
0.07938893884420395,
-0.11577611416578293,
-0.03391405940055847,
-0.018959665670990944,
-0.0038782779593020678,
0.0016288120532408357,
0.044925566762685776,
0.020874373614788055,
-0.024644967168569565,
0.03307501599192619,
0.0012503656325861812,
0.02973119542002678,
0.... | 0.038341 |
# operator import @include 'alerts/enterprise-only.mdx' @include 'alerts/alpha.mdx' The `operator import` command imports secrets from external systems in to Vault. Secrets with the same name at the same storage path will be overwritten upon import. You can write import plans that read from as many sources as you want.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/import.mdx | main | vault | [
0.05720191448926926,
0.0007734752725809813,
-0.09192519634962082,
-0.05132530629634857,
0.012608936987817287,
-0.043541569262742996,
0.026440449059009552,
-0.006879550404846668,
-0.011742264032363892,
-0.04513689875602722,
0.0005371766746975482,
-0.04443817958235741,
0.1273166984319687,
-0... | -0.051131 |
# operator init The `operator init` command initializes a Vault server. Initialization is the process by which Vault's storage backend is prepared to receive data. Since Vault servers share the same storage backend in HA mode, you only need to initialize one Vault to initialize the storage backend. This command cannot ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/init.mdx | main | vault | [
0.01256506983190775,
-0.008654367178678513,
-0.09069608151912689,
0.03288545459508896,
0.00026363664073869586,
-0.08102159202098846,
-0.04913368076086044,
-0.0003346573212184012,
0.03268158808350563,
-0.027503328397870064,
0.03707423806190491,
0.08257085829973221,
0.04843514785170555,
-0.0... | 0.012078 |
environment variables are set (CONSUL\_HTTP\_ADDR, etc). When only one Vault server is discovered, it will be initialized automatically. When more than one Vault server is discovered, they will each be output for selection. The default is false. - `-consul-service` `(string: "vault")` - Name of the service in Consul un... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/init.mdx | main | vault | [
0.021286292001605034,
-0.02848336286842823,
-0.04198941960930824,
-0.0009192111901938915,
-0.004111498594284058,
-0.02037978172302246,
0.004242566414177418,
-0.01851509138941765,
0.026624929159879684,
-0.013571633026003838,
0.06418005377054214,
-0.012613008730113506,
0.06628449261188507,
-... | -0.055054 |
# operator step-down The `operator step-down` forces the active Vault node within an [HA cluster](/vault/docs/concepts/ha) to step down from active duty. When executed against a non-active node, i.e. a standby or [performance standby](/vault/docs/enterprise/performance-standby) node, the request will be forwarded to th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/step-down.mdx | main | vault | [
-0.007678719237446785,
0.05301877483725548,
-0.03394836559891701,
0.04076521098613739,
0.02970106713473797,
-0.017612038180232048,
-0.03166269138455391,
-0.055467505007982254,
0.04612636938691139,
0.04422110691666603,
0.011989991180598736,
0.1046346127986908,
0.03835819289088249,
-0.063917... | 0.047582 |
# operator raft This command groups subcommands for operators to manage the Integrated Storage Raft backend. ```text Usage: vault operator raft [options] [args] This command groups subcommands for operators interacting with the Vault integrated Raft storage backend. Most users will not need to interact with these comma... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/raft.mdx | main | vault | [
-0.031814221292734146,
0.02774645760655403,
-0.061503197997808456,
0.029735397547483444,
0.008209045976400375,
-0.09638907760381699,
-0.016966000199317932,
-0.013027350418269634,
-0.029458925127983093,
-0.01683077961206436,
0.028826208785176277,
0.017224950715899467,
0.05260652303695679,
-... | 0.0382 |
"config": { "index": 62, "servers": [ { "address": "127.0.0.2:8201", "leader": true, "node\_id": "node1", "protocol\_version": "3", "voter": true }, { "address": "127.0.0.4:8201", "leader": false, "node\_id": "node3", "protocol\_version": "3", "voter": true } ] } } } ``` Use the output of `list-peers` to ensure that yo... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/raft.mdx | main | vault | [
-0.0003696510393638164,
-0.0022771633230149746,
-0.0021806450095027685,
0.08500803261995316,
0.0884144976735115,
0.0019307894399389625,
-0.045732125639915466,
-0.09308783710002899,
-0.018489258363842964,
0.06089925765991211,
0.018988974392414093,
0.020820077508687973,
0.024343766272068024,
... | 0.053345 |
automated snapshot utility from cloud storage. In this case, the command accepts two K=V arguments: auto\_snapshot\_config and url. $ vault operator raft snapshot load auto\_snapshot\_config=foo url=https://foo.com/blob/snapshot ``` ### snapshot restore Restores a snapshot of Vault data taken with `vault operator raft ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/raft.mdx | main | vault | [
0.013170135207474232,
0.031894978135824203,
-0.06389796733856201,
0.04124908149242401,
0.03339563310146332,
-0.046070799231529236,
-0.04895671457052231,
-0.05891123041510582,
0.011298206634819508,
0.013972846791148186,
0.04238174855709076,
-0.0008801200892776251,
0.05151361972093582,
-0.04... | 0.052468 |
type of node. On CE, this will always be `voter`. See below for an explanation of Enterprise node types. Vault Enterprise will include additional output related to automated upgrades, optimistic failure tolerance, and redundancy zones. #### Example Vault enterprise output ```text Redundancy Zones: a Servers: vault\_1, ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/raft.mdx | main | vault | [
0.0735447034239769,
-0.02425229549407959,
-0.020263539627194405,
0.025916995480656624,
0.050802525132894516,
-0.054877061396837234,
-0.026767045259475708,
-0.016761576756834984,
0.022579727694392204,
-0.00810173712670803,
0.009021841920912266,
-0.05390027165412903,
0.10208801180124283,
-0.... | 0.077064 |
guidance](/vault/docs/internals/integrated-storage#quorum-size-and-failure-tolerance) to determine the proper minimum quorum size for your cluster. - `server-stabilization-time` `(string: "10s")` - Minimum amount of time a server must be in a healthy state before it can become a voter. Until that happens, it will be vi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/raft.mdx | main | vault | [
0.05741756036877632,
-0.0013430363032966852,
-0.04011646658182144,
-0.020880473777651787,
-0.03683001548051834,
-0.008998848497867584,
-0.0993114560842514,
0.036007110029459,
-0.04838916286826134,
0.007553383708000183,
0.011408688500523567,
0.01514851488173008,
0.05851179361343384,
0.00817... | 0.007854 |
# operator rekey The `operator rekey` command generates a new set of unseal keys. This can optionally change the total number of key shares or the required threshold of those key shares to reconstruct the root key. This operation is zero downtime, but it requires the Vault is unsealed and a quorum of existing unseal ke... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/rekey.mdx | main | vault | [
0.032119132578372955,
0.007741026114672422,
-0.06089768186211586,
0.03286842629313469,
-0.07474236935377121,
0.02169700339436531,
0.02954854816198349,
-0.001847450970672071,
0.04506266489624977,
-0.009742055088281631,
0.039487965404987335,
-0.04655515402555466,
0.053603220731019974,
0.0002... | 0.015553 |
[Auto Unseal](/vault/docs/concepts/seal#auto-unseal). - `-verify` `(bool: false)` - Indicate during the phase `-init` that the verification process is activated for the rekey. Along with `-nonce` option it indicates that the nonce given is for the verification process. ### Backup options - `-backup` `(bool: false)` - S... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/rekey.mdx | main | vault | [
-0.050374746322631836,
0.02430432103574276,
-0.05719516798853874,
0.01833702251315117,
0.04068039730191231,
-0.002389573259279132,
0.01943962089717388,
-0.07001478970050812,
0.026797382161021233,
-0.04983383044600487,
0.003692978760227561,
0.01073305495083332,
0.05340249463915825,
-0.08893... | -0.081814 |
# operator diagnose The operator diagnose command should be used primarily when vault is down or partially inoperational. The command can be used safely regardless of the state vault is in, but may return meaningless results for some of the test cases if the vault server is already running. Note: if you run the diagnos... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/diagnose.mdx | main | vault | [
0.06301499903202057,
0.046387650072574615,
-0.09563938528299332,
-0.005354405380785465,
-0.02302376739680767,
-0.07833593338727951,
-0.02446497417986393,
0.0179004967212677,
-0.00281341839581728,
-0.04569506645202637,
0.030867574736475945,
0.0037330100312829018,
0.07600389420986176,
0.0353... | -0.006897 |
check the vault server config file for syntax errors. It will check for extra values in the configuration file, repeated stanzas, and stanzas that do not belong in the configuration file (for example a "tcpp" listener as opposed to a tcp listener). Currently, the `storage` stanza is not checked. #### Check storage / cr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/diagnose.mdx | main | vault | [
0.026845181360840797,
0.020797686651349068,
-0.05096558853983879,
-0.015840714797377586,
-0.031098797917366028,
-0.11378218233585358,
-0.011944864876568317,
-0.006530076265335083,
0.07185643911361694,
0.018962938338518143,
0.022524822503328323,
-0.010733920149505138,
0.07282517850399017,
0... | -0.048173 |
Vault is not accessing the consul server directly, but rather through a local agent. #### Create Vault server configuration seals `Create Vault Server Configuration Seals` creates seals from the vault configuration stanza and verifies they can be initialized and finalized. #### Check transit seal TLS `Check Transit Sea... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/diagnose.mdx | main | vault | [
0.020253986120224,
0.019445715472102165,
-0.07899659126996994,
-0.014619984664022923,
-0.002451901091262698,
-0.09269867092370987,
-0.015456866472959518,
-0.037931933999061584,
0.057772088795900345,
0.009764635935425758,
0.029650218784809113,
0.021542156115174294,
0.06207100674510002,
0.02... | -0.033057 |
# operator seal The `operator seal` seals the Vault server. Sealing tells the Vault server to stop responding to any operations until it is unsealed. When sealed, the Vault server discards its in-memory root key to unlock the data, so it is physically blocked from responding to operations unsealed. If an unseal is in p... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/seal.mdx | main | vault | [
0.03853346034884453,
0.0420372299849987,
-0.053870778530836105,
0.01717887818813324,
-0.009077214635908604,
-0.07850812375545502,
0.016249405220150948,
-0.05481990426778793,
0.02897007204592228,
-0.010303893126547337,
0.04888159781694412,
0.07138887047767639,
0.01350689958781004,
0.0122781... | 0.015201 |
# operator usage The `operator usage` command allows an administrator to retrieve a [client count](/vault/docs/concepts/client-count) report for the default reporting period, or for a specific time range of months. The command output will list clients by distinct entities, non-entity tokens, ACME clients, secret sync c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/operator/usage.mdx | main | vault | [
0.05976501479744911,
-0.003925712779164314,
-0.1000673845410347,
0.05509798228740692,
-0.013897275552153587,
-0.012362273409962654,
-0.0069187176413834095,
-0.015398145653307438,
0.07165633887052536,
-0.024762198328971863,
0.030852805823087692,
-0.022829661145806313,
0.04039151966571808,
0... | 0.023027 |
# policy The `policy` command groups subcommands for interacting with policies. Users can write, read, and list policies in Vault. For more information, please see the [policy documentation](/vault/docs/concepts/policies). ## Examples List all enabled policies: ```shell-session $ vault policy list ``` Create a policy n... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/policy/index.mdx | main | vault | [
0.01664034277200699,
0.0468657985329628,
-0.06475627422332764,
-0.03381385654211044,
0.03708849102258682,
-0.04380131885409355,
0.07456129044294357,
-0.037981223315000534,
0.019386228173971176,
0.004877993371337652,
0.02818845771253109,
0.02207936719059944,
0.08803369104862213,
0.001082991... | 0.019966 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.