This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. Because this patch is generated by a script, there may be some cosmetic changes to the layout of the YAML file(s) as the contents are normalized. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I265e47a84516982f9a470690c91ee563cf8251f0 Story: #2002586 Task: #24317
|2 years ago|
|.gitreview||2 years ago|
|.zuul.yaml||2 years ago|
|LICENSE||4 years ago|
|README.md||4 years ago|
|interface.yaml||4 years ago|
|provides.py||4 years ago|
|requires.py||4 years ago|
|test-requirements.txt||4 years ago|
|tox.ini||2 years ago|
This interface supports the integration between Barbican and HSM devices.
No explicit handler is required to consume this interface in charms that consume this interface.
The interface provides
hsm.connected state indicates that the Barbican principle charms has been
connected to. At this point the plugin data required for to configure the HSM
from Barbican should be presented.
To consume this interface in your charm or layer, add the following to
and add a provides interface of type
hsm to your charm or layers
provides: hsm: interface: barbican-hsm scope: container
Please see the example ‘Barbican SoftHSM’ charm for an example of how to author an HSM charm.
Please report bugs on Launchpad.
For development questions please refer to the OpenStack Charm Guide.