puppet-zaqar/manifests/config.pp
Tobias Urdin 0cfd8f689c Use validate_legacy
This changes all the puppet 3 validate_* functions
to use the validate_legacy function.

The validate_legacy function has been available since
about three years but require Puppet >= 4.4.0 and since
there is Puppet 4.10.12 as latest we should assume people
are running a fairly new Puppet 4 version.

This is the first step to then remove all validate function
calls and use proper types for parameter as described in spec [1].

[1] https://review.openstack.org/#/c/568929/

Change-Id: Ib31134bb604e32fd274b41dc78c4356500f71ab0
2019-02-23 23:17:56 +01:00

33 lines
822 B
Puppet

# == Class: zaqar::config
#
# This class is used to manage arbitrary zaqar configurations.
#
# === Parameters
#
# [*zaqar_config*]
# (optional) Allow configuration of arbitrary zaqar configurations.
# The value is an hash of zaqar_config resources. Example:
# { 'DEFAULT/foo' => { value => 'fooValue'},
# 'DEFAULT/bar' => { value => 'barValue'}
# }
# In yaml format, Example:
# zaqar_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 zaqar::config (
$zaqar_config = {},
) {
include ::zaqar::deps
validate_legacy(Hash, 'validate_hash', $zaqar_config)
create_resources('zaqar_config', $zaqar_config)
}