47b903239e
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. |
||
|---|---|---|
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .travis.yml | ||
| .zuul.yaml | ||
| LICENSE | ||
| README.md | ||
| interface.yaml | ||
| provides.py | ||
| requires.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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.