Tobias Urdin 7ea21f65e4 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: I503a416e4bd289649532cd29beb7548e420d0e7d
2019-02-23 23:16:35 +01:00

33 lines
846 B
Puppet

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