High-level namespace for client authentication.

The `/auth/approle` endpoint manages approle role-id & secret-id authentication functionality.

Reference: https://www.vaultproject.io/api-docs/auth/approle

The `/auth/github` endpoint manages GitHub authentication functionality.

Reference: https://www.vaultproject.io/api-docs/auth/github

The `/auth/kubernetes` endpoint manages Kubernetes authentication
functionality.

Reference: https://www.vaultproject.io/api-docs/auth/kubernetes

The `/auth/ldap` endpoint manages Lightweight Directory Access Protocol (LDAP)
authentication functionality.

Reference: https://www.vaultproject.io/api-docs/auth/ldap

The `/auth/token` endpoint manages token-based authentication functionality.

Reference: https://www.vaultproject.io/api-docs/auth/token

The `/auth/userpass` endpoint manages username & password authentication
functionality.

Reference: https://www.vaultproject.io/api-docs/auth/userpass

Main Vault client namespace. Contains functions for generic client
operations, constructing new clients, and using clients as components in a
larger system.

A _control flow handler_ defines a collection of functions which determine
how requests and responses are handled through the Vault client.

Vault HTTP client and core functions.

A mock in-memory Vault client for local testing.

High-level namespace for tracking and maintaining leases on dynamic secrets
read by a vault client.

The AWS secrets engine generates AWS access credentials dynamically based on
IAM policies.

Reference: https://www.vaultproject.io/api-docs/secret/aws

The database secrets engine is used to manage dynamically-issued credentials
for users of a database backend such as mysql, postgresql, mongodb, etc. The
vault server uses a privileged 'root' user to create new users with randomized
passwords on-demand for callers.

Reference: https://www.vaultproject.io/api-docs/secret/databases

The kv secrets engine is used to store arbitrary secrets within the
configured physical storage for Vault. Writing to a key in the kv-v1 backend
will replace the old value; sub-fields are not merged together.

Reference: https://www.vaultproject.io/api-docs/secret/kv/kv-v1

The kv secrets engine is used to store arbitrary secrets within the
configured physical storage for Vault. Writing to a key in the kv-v1 backend
will replace the old value; sub-fields are not merged together.

Reference: https://www.vaultproject.io/api-docs/secret/kv/kv-v1

The transit secrets engine handles cryptographic functions on data
in-transit. It can also be viewed as "cryptography as a service" or
"encryption as a service". The transit secrets engine can also sign and
verify data; generate hashes and HMACs of data; and act as a source of random
bytes.

Reference: https://www.vaultproject.io/api-docs/secret/transit

The `/sys/auth` endpoint is used to list, create, update, and delete auth
methods. Auth methods convert user or machine-supplied information into a
token which can be used for all future requests.

Reference: https://www.vaultproject.io/api-docs/system/auth

The `/sys/health` endpoint is used to check the health status of Vault.

Reference: https://www.vaultproject.io/api-docs/system/health

The `/sys/leases` endpoint is used to view and manage leases in Vault.

Reference: https://www.vaultproject.io/api-docs/system/leases

The `/sys/mounts` endpoint is used to manage secrets engines in Vault.

Reference: https://www.vaultproject.io/api-docs/system/mounts

The `/sys/wrapping` endpoint is used to wrap secrets and lookup, rewrap, and
unwrap tokens.

Reference:
- https://www.vaultproject.io/api-docs/system/wrapping-lookup
- https://www.vaultproject.io/api-docs/system/wrapping-rewrap
- https://www.vaultproject.io/api-docs/system/wrapping-unwrap
- https://www.vaultproject.io/api-docs/system/wrapping-wrap