)]}'
{"cloudkitty/common/custom_session.py":[{"author":{"_account_id":34975,"name":"Jaromír Wysoglad","email":"jwysogla@redhat.com","username":"jwysogla"},"change_message_id":"5a2156d294d67885efb4157c6befaa180130ed36","unresolved":true,"context_lines":[{"line_number":35,"context_line":"    return ks_session.Session(session\u003dsession, **session_options)"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"def _get_keystone_verify(conf):"},{"line_number":39,"context_line":"    \"\"\"Resolve the TLS verification setting for the keystone session."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"    Honors the cafile and insecure options of the keystone_authtoken"}],"source_content_type":"text/x-python","patch_set":3,"id":"4df539da_88d6051c","line":38,"updated":"2026-11-04 08:27:57.000000000","message":"I\u0027m not sure about the order of checking `cafile` and `insecure`. I don\u0027t think the options are mutually exclusive. I\u0027d expect the insecure to have a bigger priority here, so that when I set insecure\u003dtrue, the verification is skipped no matter what\u0027s set in cafile.","commit_id":"ef4e37fc8134da00e380c74998ef925d16fd8496"}]}