Plugin development
Advanced topic! Plugin development is a highly advanced topic in Vault, and is not required knowledge for day-to-day usage. If you don't plan on writing any plugins, we recommend not reading this section of the documentation.
Because Vault communicates to plugins over a RPC interface, you can build and distribute a plugin for Vault without having to rebuild Vault itself. This makes it easy for you to build a Vault plugin for your organization's internal use, for a proprietary API that you don't want to open source, or to prototype something before contributing it back to the main project.
In theory, because the plugin interface is HTTP, you could even develop a plugin using a completely different programming language! (Disclaimer, you would also have to re-implement the plugin API which is not a trivial amount of work.)
Developing a plugin is simple. The only knowledge necessary to write a plugin is basic command-line skills and basic knowledge of the Go programming language.
Your plugin implementation needs to satisfy the interface for the plugin type you want to build. You can find these definitions in the docs for the backend running the plugin.
Note: Plugins should be prepared to handle multiple concurrent requests from Vault.
And that's basically it! You would just need to change myPlugin
to your actual
plugin.
Building a plugin from source
To build a plugin from source, first navigate to the location holding the
desired plugin version. Next, run go build
to obtain a new binary for the
plugin. Finally,
register the
plugin and enable it.
Plugin development - resources
For more information on how to register and enable your plugin, refer to the Building Plugin Backends tutorial.
Other HashiCorp plugin development resources:
Plugin development - resources - community
See the Plugin Portal to find Community plugin examples/guides developed by community members. HashiCorp does not validate these for correctness.