From 8974f54eb97bbc7397b933e5f74e1aa9b56f19f6 Mon Sep 17 00:00:00 2001 From: Michele Baldessari Date: Mon, 20 Feb 2017 20:18:50 +0100 Subject: Improve the README for the _setting keys It is not entirely clear to someone writing their own templates how to distribute hiera keys to different roles. Let's clear this up with a more extensive description. Change-Id: I02224389c2de90bc5534bce764e5e9d3bb23538f --- puppet/services/README.rst | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) diff --git a/puppet/services/README.rst b/puppet/services/README.rst index 9c2d8c5c..e5c11535 100644 --- a/puppet/services/README.rst +++ b/puppet/services/README.rst @@ -19,8 +19,21 @@ environment to set per service parameters. Config Settings --------------- -Each service may define a config_settings output variable which returns -Hiera settings to be configured. +Each service may define three ways in which to output variables to configure Hiera +settings on the nodes. + + * config_settings: the hiera keys will be pushed on all roles of which the service + is a part of. + + * global_config_settings: the hiera keys will be distributed to all roles + + * service_config_settings: Takes an extra key to wire in values that are + defined for a service that need to be consumed by some other service. + For example: + service_config_settings: + haproxy: + foo: bar + This will set the hiera key 'foo' on all roles where haproxy is included. Deployment Steps ---------------- -- cgit 1.2.3-korg