The value with a white space should be accepted instead of being
rejected. This change fixes the wrong test case description and makes
sure the description explains what is actually tested.
Change-Id: Ieec1d030981852e9e17afcea87dd14508243f3f4
This change refactors how the dependent libraries are loaded during
unit tests, and load the libraries in the base spec_helper to avoid
duplicate and redundant implementations.
Change-Id: Id967a66f12a08da1e3ded2195cf7c3a711331347
This replaces the provider implementation of designate_config type so
that MultiStrOpt, which is used by several options like
- oslo_messaging_notifications/driver
- oslo_policy/policy_dirs
are handled correctly.
Change-Id: Ibba47194e745d37607f20316674e168d342e0f85
This patch is adding the configuration of the number of workers,
threads, and the size of the listen queue in Debian, which uses
uwsgi to run Designate API. Therefore, this patch adds a new
designate_api_uwsgi_config provider as well as a new
designate::wsgi::uwsgi class.
Change-Id: Ie007ebb4f1c861d9ac719b0d2909dbe1eb0fac16
paste_ini types/providers.
Additionally it contains patch with autorequire of designate-common
package for rootwrap_conf.
Change-Id: I64a75948f30661706ee6338448d9f662d28e871f
Partial-bug: #1440401
With the creation of the new openstack_config provider, some processing
that was done in designate_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 :
designate_config { 'DEFAULT/foo' : value => 'bar' } # will work as usual
designate_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } # will mean absent
That means that all the current :
if $myvar {
designate_config { 'DEFAULT/foo' : value => $myvar }
} else {
designate_config { 'DEFAULT/foo' : ensure => absent }
}
can be removed in favor of :
designate_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 :
designate_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
ensure_absent_val => 'foo' }
Change-Id: I16873c60bfce5b2f432f034755b7bfa3f1383dc5
Depends-On: I0eeebde3aac2662cc7e69bfad7f8d2481463a218
Currently we specify the ordering of config resources wherever it is
necessary based on the presence of the file it will write to, or the
presence of the package in charge of providing the file it will write
to.
Those kind of ordering can be specified directly at the resource level
using the autorequire mechanism. With this patch, any config resource
will make sure the package in charge of providing the file will be
installed first.
Change-Id: I8f959e4ebbce2545843a901345a2ac3daf4259a1
- The old ':should' syntax in rspec 3.x is deprecated in favor of
':expect' syntax.
Change-Id: I9a28e00e6f4ef26205a01b739b6204a8cf11dbf6
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
Takashi Kajinami