openstack/python-neutronclient
Code Issues Proposed changes

Add document for entry point in setup.cfg

Browse Source 
In addition, to remove the contrib/ way to load commands since
it is not implemented at all.

Change-Id: Id15eb10e7cb086d55d2bcad4f719f9120c6f7d1a
Closes-Bug:#1486824
This commit is contained in:
gong yong sheng 2015-08-20 11:35:36 +08:00
parent a1883b973b
commit 54e7b94012
1 changed files with 10 additions and 3 deletions

13
doc/source/devref/client_command_extensions.rst

@ -29,12 +29,19 @@ Precedence of command loading
------------------------------
* hard coded commands are loaded first
* contributed commands (those in /contrib)
* external commands (installed in the environment) are loaded last
* external commands (installed in the environment) are loaded then
Commands that have the same name will be overwritten by commands that are
loaded later. To change the execution of a command for your particular
extension you only need to override the execute method.
Currently this extension support is limited to top-level resources.
Parent/child relationships may be added if desired.
Parent/child relationships may be added if desired.
neutronclient.extension entry_point
-----------------------------------
To activate the commands in a specific extension module, add an entry in
setup.cfg under neutronclient.extension. For example:
[entry_points]
neutronclient.extension =
fox_sockets = neutronclient.neutron.v2_0.contrib._fox_sockets