)]}'
{"README":[{"author":{"_account_id":447,"name":"dan wendlandt","email":"dan@nicira.com","username":"danwent"},"change_message_id":"72c1758ef94321d2f2bea86b2cefbe3ec6dfc291","unresolved":false,"context_lines":[{"line_number":77,"context_line":"1) Identify your desired plug-in.  Choose a plugin from one of he options in"},{"line_number":78,"context_line":"   the quantum/plugins directory."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"2) Update plug-in configuration by editing the quantum.comf file and"},{"line_number":81,"context_line":"   modify the \"plugin_provider\" property to point to the location of "},{"line_number":82,"context_line":"   the Quantum plug-in."},{"line_number":83,"context_line":"   It should specify the class path to the plugin and the class name (i.e. for"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAACX%2F%2F3oc%3D","line":80,"updated":"2011-11-08 16:30:45.000000000","message":"should be \"conf\", not \"comf\" :)","commit_id":"10694894c9f506d8f3013397d73584c3ecae873a"}],"etc/quantum.conf":[{"author":{"_account_id":1726,"name":"Ghe Rivero","email":"ghe.rivero@gmail.com","username":"ghe.rivero"},"change_message_id":"f596e98e0c7d23bb1465ba22841b72b61f101e4c","unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"# Quantum plugin module"},{"line_number":22,"context_line":"plugin_provider \u003d quantum.plugins.sample.SamplePlugin.FakePlugin"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"[composite:quantum]"},{"line_number":25,"context_line":"use \u003d egg:Paste#urlmap"},{"line_number":26,"context_line":"/: quantumversions"}],"source_content_type":"text/plain","patch_set":2,"id":"AAAAC3%2F%2F9DQ%3D","line":23,"updated":"2011-12-14 09:10:16.000000000","message":"This should be under [PLUGIN] section, and with name provider... or change the quantum/common/utils.py to config.get(\"DEFAULT\",\"plugin_provider\"), but the first option is more backward compatible.","commit_id":"fcc4ad0b757b26c0e0365d50032bb757fd39f2a8"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"unresolved":false,"context_lines":[{"line_number":20,"context_line":""},{"line_number":21,"context_line":"# Quantum plugin module"},{"line_number":22,"context_line":"plugin_provider \u003d quantum.plugins.sample.SamplePlugin.FakePlugin"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"[composite:quantum]"},{"line_number":25,"context_line":"use \u003d egg:Paste#urlmap"},{"line_number":26,"context_line":"/: quantumversions"}],"source_content_type":"text/plain","patch_set":2,"id":"AAAAD3%2F%2F%2FZc%3D","line":23,"in_reply_to":"AAAAC3%2F%2F9DQ%3D","updated":"2012-01-10 18:06:53.000000000","message":"Hi Ghe,\n\nactually the method you\u0027re mentioning is used when loading from plugins.ini. \nI\u0027ve tried to add a [plugin] section to the pastedeploy configuration file, as it would actually be cleaner in this way, but unfortunately only the options in the [DEFAULT] section are passed to factory method which initializes the plugin.","commit_id":"fcc4ad0b757b26c0e0365d50032bb757fd39f2a8"}]}