)]}'
{"oslo_messaging/transport.py":[{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"e406ad31a00ddf0246bd01f502f5e79ff44efc93","unresolved":false,"context_lines":[{"line_number":42,"context_line":"                    \u0027full configuration.\u0027),"},{"line_number":43,"context_line":"    cfg.StrOpt(\u0027rpc_backend\u0027,"},{"line_number":44,"context_line":"               deprecated_for_removal\u003dTrue,"},{"line_number":45,"context_line":"               deprecated_reason\u003d\"Replaced by [DEFAULT]/transport_url\","},{"line_number":46,"context_line":"               default\u003d\u0027rabbit\u0027,"},{"line_number":47,"context_line":"               help\u003d\u0027The messaging driver to use, defaults to rabbit. Other \u0027"},{"line_number":48,"context_line":"                    \u0027drivers include amqp and zmq.\u0027),"}],"source_content_type":"text/x-python","patch_set":2,"id":"dab17558_b14b2186","line":45,"updated":"2016-05-18 01:20:25.000000000","message":"If the entire rpc_backend option is being deprecated, we should mark all of the other drivers impl-specific options as deprecated, not just rabbit, right?\n\nAnd what about zeromq? You mentioned that it can\u0027t use \u0027transport_url\u0027. Does that mean it\u0027s not possible or does it just mean work needs to be done?","commit_id":"a5dd33b2fd3a8b759f8716b4d2b1c9df4f76dd44"},{"author":{"_account_id":2813,"name":"Mehdi Abaakouk","email":"sileht@sileht.net","username":"sileht"},"change_message_id":"3f4b359958c0600ec826f7d5fe61658011a4a69b","unresolved":false,"context_lines":[{"line_number":42,"context_line":"                    \u0027full configuration.\u0027),"},{"line_number":43,"context_line":"    cfg.StrOpt(\u0027rpc_backend\u0027,"},{"line_number":44,"context_line":"               deprecated_for_removal\u003dTrue,"},{"line_number":45,"context_line":"               deprecated_reason\u003d\"Replaced by [DEFAULT]/transport_url\","},{"line_number":46,"context_line":"               default\u003d\u0027rabbit\u0027,"},{"line_number":47,"context_line":"               help\u003d\u0027The messaging driver to use, defaults to rabbit. Other \u0027"},{"line_number":48,"context_line":"                    \u0027drivers include amqp and zmq.\u0027),"}],"source_content_type":"text/x-python","patch_set":2,"id":"bab6814e_65556c1c","line":45,"in_reply_to":"dab17558_b14b2186","updated":"2016-05-18 07:11:44.000000000","message":"rpc_backend is just a backward compatibility thing for the old rpc lib. It\u0027s exactly the same as the scheme in the transport_url.\n\nSo rpc_backend\u003dzmq becomes transport_url\u003dzmq://\n\nAbout drivers impl-specific options, transport_url currently replace only \u0027hosts\u0027, \u0027user\u0027, \u0027password\u0027 and \u0027virtualhost\u0027. zeromq for example doesn\u0027t have this concept\n\nOnly rabbit defines them, other already only uses the TransportURL object to get these informations.\n\nAn example of future enhancement could be a way to read the drivers impl-specific options from the transport_url too (with the query string). But the argument against this idea is how to cleanly document theses options, the option documnetations is currently very complete for deployer (thx to oslo.config), moving all of them in query_string can be confusing.","commit_id":"a5dd33b2fd3a8b759f8716b4d2b1c9df4f76dd44"}]}
