With the creation of the new openstack_config provider, some processing
that was done in trove_config has been centralized in
openstack_config.
The same apply for trove_conductor_config, trove_guestagent_config and
trove_taskmanager_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 :
trove_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual
trove_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent
That means that all the current :
if $myvar {
trove_config { 'DEFAULT/foo' : value => $myvar }
} else {
trove_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
trove_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 :
trove_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: I44472b107c951d22932c533031f68aa67a5f2e18
Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218
c8527beace