Carlos Camacho 44ef2a3ec1 Change template names to rocky
The new master branch should point now to rocky.

So, HOT templates should specify that they might contain features
for rocky release [1]

Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.

[1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky
Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
2018-05-09 08:28:42 +02:00

63 lines
2.0 KiB
YAML

heat_template_version: rocky
description: >
Barbican API KMIP backend configured with Puppet
parameters:
# Required default parameters
ServiceData:
default: {}
description: Dictionary packing service data
type: json
ServiceNetMap:
default: {}
description: Mapping of service_name -> network name. Typically set
via parameter_defaults in the resource registry. This
mapping overrides those in ServiceNetMapDefaults.
type: json
DefaultPasswords:
default: {}
type: json
RoleName:
default: ''
description: Role name on which the service is applied
type: string
RoleParameters:
default: {}
description: Parameters specific to the role
type: json
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
BarbicanKmipStoreUsername:
description: Username to connect to KMIP device
type: string
BarbicanKmipStorePassword:
description: Password to connect to KMIP device
type: string
hidden: true
BarbicanKmipStoreHost:
description: Host for KMIP device
type: string
BarbicanKmipStorePort:
description: Port for KMIP device
type: number
BarbicanKmipStoreGlobalDefault:
description: Whether this plugin is the global default plugin
type: boolean
default: false
outputs:
role_data:
description: Role data for the Barbican KMIP crypto backend.
value:
service_name: barbican_backend_kmip
config_settings:
barbican::plugins::kmip::kmip_plugin_username: {get_param: BarbicanKmipStoreUsername}
barbican::plugins::kmip::kmip_plugin_password: {get_param: BarbicanKmipStorePassword}
barbican::plugins::kmip::kmip_plugin_host: {get_param: BarbicanKmipStoreHost}
barbican::plugins::kmip::kmip_plugin_port: {get_param: BarbicanKmipStorePort}
barbican::plugins::kmip::global_default: {get_param: BarbicanKmipStoreGlobalDefault}