| Thread Previous • Date Previous • Date Next • Thread Next |
Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2359
** Bug watch added: github.com/canonical/cloud-init/issues #2359
https://github.com/canonical/cloud-init/issues/2359
** Changed in: cloud-init
Status: Triaged => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1120595
Title:
Use entrypoints for config modules/distros/handlers
Status in cloud-init:
Expired
Bug description:
Instead of having our own custom way of loading modules and imports it
appears that the concept of entrypoints in python is the defacto way
of exposing& loading these types of 'plugins'. It would probably be
nice to use that ourselves, thus allowing people to use a well
understood way of hooking into cloud-init instead of having to
understand a cloud-init 'custom' way.
http://pythonhosted.org/distribute/pkg_resources.html#entry-points
OpenStack is using http://pypi.python.org/pypi/stevedore, perhaps we
should?
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1120595/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
