This repo was created by accident, use deb-python-oslo.config
instead.
Needed-By: I1ac1a06931c8b6dd7c2e73620a0302c29e605f03
Change-Id: I81894aea69b9d09b0977039623c26781093a397a
There was already a PortOpt, but this is not composable with ListOpt.
The new type inherits from Integer and therefore supports min/max
value and choices. For example, openstack/vmware-nsx wants to use this
to configure a default list of ports for a firewall rule.
Change-Id: I83bbec6add8ce2951e94e69ec14bb6d8137d4f0c
Allows for an option to be tagged with advanced true/
false, notifying the end user about uncommon usage.
Such an option is not normally used, and will be
moved to the bottom of the respective namespace.
Only options set to true (default: false) will be
tagged as such in generated sample files.
Change-Id: I2689aba283e473bb293bf0cf0c1c4bcb5979d115
Implements: blueprint advanced-option
The sphinx extension depends on all of the help text associated with an
option being regular strings. When oslo_i18n's lazy translation feature
is turned on, the marker functions return Message objects that do not
support all of the features of strings. Add a step to turn off lazy
evaluation when the oslo_context.sphinxext extension is activated.
Change-Id: Icaec4691135cd07d96994f01498e0f9d2e09af58
Closes-Bug: #1605648
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit adjusts sentence about option name and group in
error messages to make it more clear and friendly.
TrivialFix
Change-Id: I0f23e9e0ff0499509621c5ae7b1fc4573d6037a7
Just like Integers, Floats configuration should also have a minimum and
maximum possible values.
For example, the vmware-nsx plugin needs it for the QoS support.
See https://review.openstack.org/#/c/344763/
Change-Id: If1c47444e0c12b68d9d9cb645b8251e4462cfd49
Many assertEqual sentences don't follow assertEqual(expected, actual),
this patch fix all of them.
Change-Id: Ia2fbad7a952039fbba4cddc3308721a19dd099d1
Closes-Bug: 1604213
Currently StrOpt has a max_length parameter to restrict the length
of the value, but URIOpt does not. The keystone project actually
has use for a max_length to restrict a URI used for the SAML2
entity ID.
Reference patch:
https://review.openstack.org/#/c/341514
Change-Id: I39d012b0b7ebeddf6067016487ac8258461dda30
We landed the feature to let the sphinx integration work with multiple
input and output files, but we didn't update the docs for it.
Change-Id: I1ef3f91aed3bdbcfdff4f8afc5fa325b34008495
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: I688d8d5ded43878cc3330d67c7749c208d821767
After https://review.openstack.org/#/c/334014/, loading
NamedExtensionManager will fail when names is not an
iterable. In test test_list_ignores_doubles we are passing
None as namespace so it's failing.
Change-Id: I98e083c88a9d3db90bfeb9d5019d85bf01db6ca8
It is possible to deprecate an option, but there's no clear way to
state when this deprecation occured and when the option will actually
go away. This leaves the user with a decision to make. Nova, for
example, frequently includes the release that the option was removed in
as part of the help message like so:
"memcached_servers" opt is deprecated in Mitaka. In Newton release
oslo.cache config options should be used as this option will be
removed.
This is a decision that the user shouldn't have to make. Add a
'deprecated_since' parameter to allow users to specify this information
in a uniform manner. The parameter allows for any string value.
A future work item would add a hacking or tox check to compare this
parameter against the expected deprecation version. For example, to
ensure all Nova parameters deprecated in '13.0' should be removed in
'14.0'. This will be done on a per-project basis.
Change-Id: Ic894358006606f123e31611f068d9b6192d42616
This allows fixture to check config option's type and value before
overriding, that ensure testing as same as production enviroment.
Change-Id: I958d04c92cfeacd134aaf2e0a758e0defdb607e2
Currently, we raise NoSuchOptError in case config files were not parsed
yet, which does not seem like correct behaviour for the property (since
it is never expected to be an option defined).
Instead of raising, let's return an empty list.
Related-Bug: #1587359
Change-Id: Ia66e9d26b011c0f7bd3d1383d9282554cf300f29
List type allows to pass string values as default values, which are then
handled by splitting on commas. For formatting matters, if the default
value is of string type, there is no special conversion needed, and we
can reuse the value as-is.
Change-Id: Ie9ecdfc064e886f6138b1fa9e839d8f95a7df339
Closes-Bug: #1586366
Required options currently are not pushed to the
top of each section, and they are also not marked
as required. This will mark the option as required
and push it to the top, uncommented. This will
allow users to know for sure what options are
minimally required to get the service started.
Change-Id: Ic194498ec695d268cce0a26d19f9469ba800412e
Implements: blueprint oslo-generator-required
Andreas Jaeger