openstack
/
charm-vault
Code Issues Proposed changes
charm-vault/src
History
James Page aa4a55e31a Add ssl-ca configuration option 
Allow charm users to provide the SSL Root CA certificate, supporting
the use of an internal Root CA for PKI signing.

This CA certificate will be provided to charms directly consuming
the Vault HTTPS API.

Change-Id: I866e9835c0f47236c160e8ff122eb2cb4fc3f053
 		2018-04-12 17:14:59 +01:00
..
files/nagios Restructure charm to follow src dir format 2018-02-19 10:19:09 +00:00
reactive Add ssl-ca configuration option 2018-04-12 17:14:59 +01:00
templates Restructure charm to follow src dir format 2018-02-19 10:19:09 +00:00
tests Add functional tests 2018-04-12 11:20:16 +00:00
README.md Restructure charm to follow src dir format 2018-02-19 10:19:09 +00:00
config.yaml Add ssl-ca configuration option 2018-04-12 17:14:59 +01:00
copyright Restructure charm to follow src dir format 2018-02-19 10:19:09 +00:00
layer.yaml Restructure charm to follow src dir format 2018-02-19 10:19:09 +00:00
metadata.yaml Add functional tests 2018-04-12 11:20:16 +00:00
test-requirements.txt Add functional tests 2018-04-12 11:20:16 +00:00
tox.ini Add functional tests 2018-04-12 11:20:16 +00:00

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 storage backend only.

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.