tripleo-heat-templates/environments/barbican-backend-kmip.yaml
Dan Prince 5e46c2a579 flatten the barbican service configurations
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration
for the barbican API service. The barbican backend files are also
moved into the deployment/barbican directory for consistency.

Change-Id: Ib4a3993ac352e9e00f72ddf374042b574f6d55d6
Related-Blueprint: services-yaml-flattening
2019-02-18 08:06:21 -05:00

16 lines
751 B
YAML

# A Heat environment file to enable the barbican KMIP backend. Note
# that barbican needs to be enabled in order to use this.
parameter_defaults:
# In order to use this backend, you need to uncomment this value and
# provide an appropriate KEK that barbican will use to encrypt secrets
# in the database.
#
# BarbicanKmipStoreUsername: Username to connect to KMIP device
# BarbicanKmipStorePassword: Password to connect to KMIP device
# BarbicanKmipStoreHost: Host for KMIP device
# BarbicanKmipStorePort: Port for KMIP device
# BarbicanKmipStoreGlobalDefault: Whether this plugin is the global default plugin
resource_registry:
OS::TripleO::Services::BarbicanBackendKmip: ../deployment/barbican/barbican-backend-kmip-puppet.yaml