Introduce keystone:config
This keystone::config is aim to use keystone_config resources to manage custom configurations in keystone config files. This will make end user easy to add their own custom options in Hiera data. Fully implements blueprint keystone-custom-config Change-Id: I1e0742382bfca3f627029c7f17fe05fd9d3d0dbe
This commit is contained in:
30
manifests/config.pp
Normal file
30
manifests/config.pp
Normal file
@@ -0,0 +1,30 @@
|
||||
# == Class: keystone::config
|
||||
#
|
||||
# This class is used to manage arbitrary keystone configurations.
|
||||
#
|
||||
# === Parameters
|
||||
#
|
||||
# [*keystone_config*]
|
||||
# (optional) Allow configuration of arbitrary keystone configurations.
|
||||
# The value is an hash of keystone_config resources. Example:
|
||||
# { 'DEFAULT/foo' => { value => 'fooValue'},
|
||||
# 'DEFAULT/bar' => { value => 'barValue'}
|
||||
# }
|
||||
# In yaml format, Example:
|
||||
# keystone_config:
|
||||
# DEFAULT/foo:
|
||||
# value: fooValue
|
||||
# DEFAULT/bar:
|
||||
# value: barValue
|
||||
#
|
||||
# NOTE: The configuration MUST NOT be already handled by this module
|
||||
# or Puppet catalog compilation will fail with duplicate resources.
|
||||
#
|
||||
class keystone::config (
|
||||
$keystone_config = {},
|
||||
) {
|
||||
|
||||
validate_hash($keystone_config)
|
||||
|
||||
create_resources('keystone_config', $keystone_config)
|
||||
}
|
||||
Reference in New Issue
Block a user