the validate_legacy function is marked for deprecation in
v9.0.0 from puppetlabs-stdlib.
Note that this change looses validation about pool ids. Alternatively
we can define a new data type to keep the validation, but these defined
types for pool-manager were already deprecated and useless and will be
removed in a near future release so we avoid that redundant step.
Change-Id: I85d7058bf379c6aa0e787b2f806f14aebf0693d3
manifests/config.pp:7:WARNING: No matching class parameter for
documentation of designate::config::xxx_config
manifests/init.pp:15:WARNING: No matching class parameter for
documentation of designate::service_ensure
Change-Id: Idacc31cf50ce2bc5774a4b3552161e489d0174d4
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: If8c450da479eca3167d93a1ef29ac8b1bc4312ca
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
Change-Id: If9fa188b7dca47e6724a737d66e34c0c85668c36
this path aims to add designate_rootwrap_config
in designate::config.
use designate config resources to manage
custom configurations in rootwrap config files.
Change-Id: Iee8aa66ff6464f387664d2a0571f6e6ad685dc2b
This ensures that all parameters are documented and includes fixes to
existing undocumented parameters or incorrectly formatted docs.
Change-Id: I14c093214e45ad3b14123e16ee8ccf309ba45978
This designate::config is aim to use designate config resources
to manage custom configurations in designate config files.
This will make end user easy to add their own custom options
in Hiera data.
Fully implements blueprint designate-custom-config
Change-Id: I11a4cd53ae68113341e8b0851c68c9d09c362e86