Deprecate allow_sorting and allow_pagination options
There is no technical reason to disable sorting and pagination, except maybe performance concerns. But there are other ways to DoS-attack neutron-server services, like... any other type of request. So the concern is moot. Keeping those options available for configuration reduces compatibility between Neutron installations. It's better to do the right thing, and do it right, implementing the feature for the benefit of API users. DocImpact Update configuration documentation to reflect deprecation. Change-Id: Iad26221a58589b10381f1a0d69a88c92fb5adeee Related-Bug: #1566514
This commit is contained in:
parent
9733cc2552
commit
fdf66024d3
@ -54,9 +54,14 @@ core_opts = [
|
||||
cfg.BoolOpt('allow_bulk', default=True,
|
||||
help=_("Allow the usage of the bulk API")),
|
||||
cfg.BoolOpt('allow_pagination', default=True,
|
||||
help=_("Allow the usage of the pagination")),
|
||||
deprecated_for_removal=True,
|
||||
help=_("Allow the usage of the pagination. This option has "
|
||||
"been deprecated and will now be enabled "
|
||||
"unconditionally.")),
|
||||
cfg.BoolOpt('allow_sorting', default=True,
|
||||
help=_("Allow the usage of the sorting")),
|
||||
deprecated_for_removal=True,
|
||||
help=_("Allow the usage of the sorting. This option has been "
|
||||
"deprecated and will now be enabled unconditionally.")),
|
||||
cfg.StrOpt('pagination_max_limit', default="-1",
|
||||
help=_("The maximum number of items returned in a single "
|
||||
"response, value was 'infinite' or negative integer "
|
||||
|
@ -0,0 +1,4 @@
|
||||
---
|
||||
deprecations:
|
||||
- The ``allow_sorting`` and ``allow_pagination`` configuration options
|
||||
are deprecated and will be removed in a future release.
|
Loading…
x
Reference in New Issue
Block a user