d686122ce7
With the creation of the new openstack_config provider, some processing that was done in keystone_config has been centralized in openstack_config. Impacted methods are : * section * setting * separator Also, this commit adds the fact that, when passing a specific string (ensure_absent_val) the provider will behave as if ensure => absent was specified. '<SERVICE DEFAULT>' is the default value for ensure_absent_val. The use case is the following : keystone_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual keystone_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent That means that all the current : if $myvar { keystone_config { 'DEFAULT/foo' : value => $myvar } } else { keystone_config { 'DEFAULT/foo' : ensure => absent } } can be removed in favor of : keystone_config { 'DEFAULT/foo' : value => $myvar } If for any reason '<SERVICE DEFAULT>' turns out to be a valid value for a specific parameter. One could by pass that doing the following : keystone_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>', ensure_absent_val => 'foo' } Change-Id: I7c880518f0323e44e7c72f0ff5548482a0b1413c Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218 |
||
---|---|---|
.. | ||
ini_setting.rb |