Added API extensions to detect sorting/pagination features
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Ihar Hrachyshka | ||
openstack-api-site |
Invalid
|
Undecided
|
Unassigned |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 5e0878f476d7116
Author: Ihar Hrachyshka <email address hidden>
Date: Tue Jun 14 16:16:06 2016 +0200
Added API extensions to detect sorting/pagination features
Those features are available only when allow_sorting and
allow_
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-
api_extensions option in tempest.conf.
Now that DEFAULT_
used in a single place only (in allow_sorting/
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: I0aaaa037a8ad52
Changed in neutron: | |
assignee: | nobody → Ihar Hrachyshka (ihar-hrachyshka) |
Changed in neutron: | |
assignee: | Ihar Hrachyshka (ihar-hrachyshka) → Akihiro Motoki (amotoki) |
Fix proposed to branch: master /review. openstack. org/362877
Review: https:/