)]}'
{"etc/ironic/ironic.conf.sample":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"dca92932119fe964f605009e6557c1572200c849","unresolved":false,"context_lines":[{"line_number":222,"context_line":"# various testing frameworks but not intended for use in"},{"line_number":223,"context_line":"# production. Turning on this option will disable all non-"},{"line_number":224,"context_line":"# testing drivers. (boolean value)"},{"line_number":225,"context_line":"#use_testing_drivers\u003dfalse"},{"line_number":226,"context_line":""},{"line_number":227,"context_line":""},{"line_number":228,"context_line":"#"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"da86d52c_6d8d2d7c","line":225,"updated":"2015-02-10 21:59:32.000000000","message":"Since this is a Boolean, I\u0027d interpret it to be: if True, in addition to ironic.drivers, use/allow ironic.testing_drivers. If False, only allow ironic.drivers.\n\nI think if we want to allow drivers OR testing_drivers, I\u0027d prefer a config that was something like ... \n  # Which set of drivers to load. Possible values are \n  # \u0027drivers\u0027 or \u0027testing_drivers\u0027.\n  #driver_namespace\u003ddrivers\n\nI\u0027m not sure I like the prod-or-test-but-not-both-without-going-through-hoops option. We don\u0027t know peoples\u0027 use cases, and I don\u0027t see why we\u0027d make it more difficult for them to mix. I think that putting the testing_drivers in a separate list makes sense. The two lists in setup.cfg and a config to allow for testing drivers makes it explicit that they have to do something to use both. It would also be backwards compatible.\n\nWhat\u0027s the rationale for NOT allowing drivers from both?","commit_id":"cc618b88e06e8044e5fba847506d901f5e53a744"}]}