8f726129b2
This method retrieves the extensions loaded by the Neutron API, instead of reading the configured extensions in the tempest configuration. This method can help during a extension implementation, as for example in "subnet-external-network". This extension cannot be declared yet in the neutron-tempest-plugin job definitions, because the extension has not been implemented in Neutron. However, when the Neutron patch is tested, the extension is missing in the configuration and the test cannot correctly modify the API calls. Related-Bug: #2051831 Change-Id: I3e6f570cd63e44df7ceb8f5013c2b4adebfe4286 |
||
---|---|---|
.. | ||
api | ||
bgpvpn | ||
common | ||
fwaas | ||
neutron_dynamic_routing | ||
scenario | ||
services | ||
sfc | ||
tap_as_a_service | ||
vpnaas | ||
__init__.py | ||
config.py | ||
exceptions.py | ||
plugin.py | ||
README.rst |
WARNING
Some files under this path were copied from tempest as part of the move of the api tests, and they will be removed as required over time to minimize the dependency on the tempest testing framework. While it exists, only neutron_tempest_plugin.* should be importing files from this path. neutron_tempest_plugin.config uses the global cfg.CONF instance and importing it outside of the api tests has the potential to break Neutron's use of cfg.CONF.