Comment 16 for bug 1217017
Revision history for this message
| David Stanek (dstanek) wrote Re: dependency injection fails to init domain-specific identity drivers | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
The title for this is a little misleading. It's not the DI that is failing, it's the loading of the driver[1]. The code assumes that all of the drivers will be constructed with the config options from the domain specific config.
While the provided fix works (stops the traceback), I don't think it's the right one. The drivers should all be accepting the ConfigOpts instance in their __init__ and use it instead of the global conf. This would allow the driver to be configured by the domain specific file.
1. http://