bae3706150
The file was originally crafted by hand, and any future proposed updates would have resulted in a large (mostly superfluous) diff. This just gets ahead of that, as we look at ways to ramp up test definition automation. Change-Id: Ib99041a418dd4ccee8a3844f1cf7b2eecc56b5dd |
||
|---|---|---|
| .. | ||
| actions | ||
| files/nagios | ||
| lib/charm | ||
| reactive | ||
| templates | ||
| tests | ||
| README.md | ||
| actions.yaml | ||
| config.yaml | ||
| copyright | ||
| icon.svg | ||
| layer.yaml | ||
| metadata.yaml | ||
| test-requirements.txt | ||
| tox.ini | ||
| wheelhouse.txt | ||
README.md
Overview
Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing. Vault handles leasing, key revocation, key rolling, and auditing. Through a unified API, users can access an encrypted Key/Value store and network encryption-as-a-service, or generate AWS IAM/STS credentials, SQL/NoSQL databases, X.509 certificates, SSH credentials, and more.
About the Charm
This charm installs Vault from the Ubuntu Snap Store and supports the PostgreSQL and MySQL storage backends. Note that Vault itself does not support PostgreSQL 10, so neither does this charm. If you're deploying on bionic, you'll need to deploy a 9.x version of PostgreSQL.
After deploying and relating the charm to postgresql, install the vault snap locally and use "vault init" to create the master key shards and the root token, and store them safely.
Network Spaces support
The vault charm directly supports network binding via the 'access' extra-binding and the 'cluster' peer relation. These allow the Vault API and inter-unit Cluster addresses to be configured using Juju network spaces.