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 key/value
pair, seen below.
Examples
Display information about a plugin
$ vault plugin info -version=v1.0.0 auth my-custom-pluginKey Value--- -----args []builtin falsecommand my-custom-plugindeprecation_status n/aname my-custom-pluginsha256 04ce575260fa3a2cfc477d13ac327108c50838a03917ec4d6df38ecdc64452d1version v1.0.0$ vault plugin info database postgresql-database-pluginKey Value--- -----args []builtin truecommand n/adeprecation_status supportedname postgresql-database-pluginsha256 n/aversion n/aUsage
The following flags are available in addition to the standard set of flags included on all commands.
Output options
-field(string: "")- Print only the field with the given name. Specifying this option will take precedence over other formatting directives. The result will not have a trailing newline making it ideal for piping to other processes.-format(string: "table")- Print the output in the given format. Valid formats are "table", "json", or "yaml". This can also be specified via theVAULT_FORMATenvironment variable.
Command options
-plugin-version(string: "")- Semantic version of the plugin to read from the catalog. If unspecified, refers to the unversioned plugin registered with the same name and type, or the built-in plugin, in that order of precedence.