Charm Interface - Barbican Secrets plugin

Go to file

Frode Nordahl ea50b1e502 Initial commit of charm interface skeleton		2018-10-11 11:46:45 +02:00
unit_tests	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
.gitignore	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
.stestr.conf	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
LICENSE	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
README.md	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
interface.yaml	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
test-requirements.txt	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00
tox.ini	Initial commit of charm interface skeleton	2018-10-11 11:46:45 +02:00

README.md

Overview

This interface supports the integration between Barbican and secrets stores.

Usage

No explicit handler is required to consume this interface in charms that consume this interface.

The interface provides secrets.connected and secrets.available states.

For an secrets subordinate charm

The secrets.connected state indicates that the Barbican principle charms has been connected to. At this point the plugin data required for to configure the secrets store from Barbican should be presented.

metadata

To consume this interface in your charm or layer, add the following to layer.yaml:

includes: ['interface:barbican-secrets']

and add a provides interface of type secrets to your charm or layers metadata.yaml:

provides:
  secrets:
    interface: barbican-secrets
    scope: container

Please see the example 'Barbican Vault' charm for an example of how to author an secrets store charm.

Bugs

Please report bugs on Launchpad.

For development questions please refer to the OpenStack Charm Guide.