In ksa, plugins loading is managed by ksa.
OpenStackClient token_endpoint plugin expects get_auth_ref[1],
(a method consistent with ksa auth plugins) which is not implemented
in ksa token_endpoint.
This change will not change overall ksa behavior, as it only makes
OpenStackClient to be able to provide its token_endpoint plugin,
necessary for authentication migration in osc from ksc to ksa[2].
[1] https://github.com/openstack/python-openstackclient/blob/
master/openstackclient/api/auth_plugin.py#L48-L50
[2] http://docs.openstack.org/developer/keystoneauth/migrating.html
Change-Id: I7d8f9a9f071a0d37244f8985bd7d09d49ba79eb8
Closes-Bug: 1533369
One of the issues raised with keystoneclient plugins is the way that
loading of a plugin is mixed in with the definition of a plugin. Amongst
other things this really meant that there was only one way to utilize
each plugin class, to do another plugin that utilized an existing one
you would have to define a new class and proxy to it.
In this patch we split the concerns. There is a whole new section called
loading that is solely responsible for ways to load the auth plugin from
CLI or from argparse and other future methods.
This new section will likely be split into its own repository.
Change-Id: I8387b86fc0e3a8403f9806440196e8723eaf1ee4
The /auth directory made sense when we were seperating the plugins from
the rest of keystoneclient, however now we are in keystoneauth there
really is no need for the auth subdirectory.
Change-Id: I94f12780af4f914ead93796a052e9dc82c6c2f81