)]}'
{"specs/tempest-library.rst":[{"author":{"_account_id":1192,"name":"David Kranz","email":"dkranz@redhat.com","username":"david-kranz"},"change_message_id":"bb40f184c9145365c33806542826deca0826a356","unresolved":false,"context_lines":[{"line_number":128,"context_line":" * Copy and convert the Tempest REST Client"},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"   * Clean up the REST Client code"},{"line_number":131,"context_line":"   * Separate the base REST Client code from Tempest specific code"},{"line_number":132,"context_line":"   * Move the REST Client specific exception to base REST Client code"},{"line_number":133,"context_line":"   * Copy the base REST Client code to tempest-lib repository"},{"line_number":134,"context_line":"   * Switch Tempest to use the base REST Client code of tempest-lib"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_6b4524b2","line":131,"updated":"2014-12-10 19:52:19.000000000","message":"This is not so straightforward. Originally I thought there were just a few tempest conf values that could be made into a dict argument to the rest client. But now I see these:\n\ncompute.build_interval\ncompute.build_timeout\nidentity.disable_ssl_certificate_validation\nidentity. ca_certificates_file\nidentity.region\ndebug.trace_requests\nThe catalog_type and region and endpoint_type for each service section\n\nThis list makes me think it would be better to define a \"conf\" argument to the rest client with the interface of an attribute dict of some kind.","commit_id":"d27fb0779cc779970810f545f966773746efe03a"}]}