Open Stack

On 03/23/2018 05:43 PM, Wojciech Dec wrote:
> Hi All,
> 
> I'm converting a few heat service templates that have been working ok
> with puppet3 modules to run with Puppet 4, and am wondering if there is
> a way to pass an "undefined" default via heat to allow "default" values
> (eg params.pp) of the puppet modules to be used?
> The previous (puppet 3 working) way of passing an empty string in heat
> doesn't work, since Puppet 4 interprets this now as the actual setting.

yaml allows use of ~ to represent null

it looks like in a hiera lookup that is resolved as the "nil" value, not
sure if that is enough to make the default values for a class to apply

-- 
Giulio Fidente
GPG KEY: 08D733BA