5e0878f476
Those features are available only when allow_sorting and allow_pagination options are enabled (the current default is False). They don't depend on plugin support, because when plugins don't implement them natively, emulated mode is applied by API router itself. So to make it plugin agnostic, we introduce a way to register custom per-extension checks to override support detection for cases like that one. Now that we have a way to detect support for those features via API, there is little reason to keep tempest configuration options to enable those features. Instead, just inspect [network-feature-enabled] api_extensions option in tempest.conf. Now that DEFAULT_ALLOW_SORTING/DEFAULT_ALLOW_PAGINATION constants are used in a single place only (in allow_sorting/allow_pagination definitions), removed them and replaced with a literal. Added first in-tree API tests for /extensions entry point. DocImpact Update API documentation to cover new extensions. APIImpact Document the new extensions. Related-Bug: #1566514 Change-Id: I0aaaa037a8ad52060a68dd75c0a1accc6add238e
7 lines
270 B
YAML
7 lines
270 B
YAML
---
|
|
features:
|
|
- New API extensions, 'sorting' and 'pagination', have been added to allow
|
|
API users to detect if sorting and pagination features are enabled. These
|
|
features are controlled by ``allow_sorting`` and ``allow_pagination``
|
|
configuration options.
|