)]}'
{"manifests/keystone/authtoken.pp":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"382cb1a8d5a8094a0174ca13b18259fd9eeb5f21","unresolved":false,"context_lines":[{"line_number":229,"context_line":"    username                       \u003d\u003e $username,"},{"line_number":230,"context_line":"    password                       \u003d\u003e $password,"},{"line_number":231,"context_line":"    project_name                   \u003d\u003e $project_name,"},{"line_number":232,"context_line":"    config_group                   \u003d\u003e \u0027keystone_auth\u0027,"},{"line_number":233,"context_line":"    auth_url                       \u003d\u003e $auth_url,"},{"line_number":234,"context_line":"    www_authenticate_uri           \u003d\u003e $www_authenticate_uri,"},{"line_number":235,"context_line":"    auth_version                   \u003d\u003e $auth_version,"}],"source_content_type":"text/x-puppet","patch_set":1,"id":"9f560f44_87539b6c","line":232,"range":{"start_line":232,"start_character":4,"end_line":232,"end_character":54},"updated":"2020-09-01 14:37:19.000000000","message":"Is this actually valid way from keystonemiddleware perspective ?\nAFAIK the section name keystone_authtoken is hard-coded in keystonemiddleware and we don\u0027t expect overrides about the config section it refers to.\n\nI think the proper direction here would be to add an independent class like magnum::auth or magnum::keystone_auth and then manage paramer for the keystone_auth section, but please correct me if I missed any individual implementation in Magnum.","commit_id":"165fabff5ef083a6a011b74048f2ca6b40bca4d8"}]}