)]}'
{"goals/proposed/migrate-policy-format-from-json-to-yaml.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ece2a94ad55270e793c35f44a657e318f6c22e29","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"#. Change the default for config ``policy_file`` via ``set_defaults``."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"#. Deprecate the JSON format support via warnings in doc and release notes."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Once all project finish this, we will be able to deprecate it in Oslo policy"},{"line_number":66,"context_line":"also which allow policy deprecation without causing pain to OpenStack deployers."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f621f24_97764806","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":75},"updated":"2020-10-29 22:32:42.000000000","message":"It would be really helpful to have sample text for this because it\u0027s difficult to describe what this means at the (for example) Cinder project level.  It\u0027s clear that oslo can deprecate and remove JSON policy file generation, but given that YAML is a superset of JSON, an operator can still give Cinder a policy file full of JSON and it will work just fine.  So in that sense, Cinder still supports a JSON policy file, we just believe that it would be a bad idea to use such a file.","commit_id":"9a53610a57a7b8c29b27f42381d4e02f83234123"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7a94477d9d064d3842a95e41a285ba832b74d33c","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"#. Change the default for config ``policy_file`` via ``set_defaults``."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"#. Deprecate the JSON format support via warnings in doc and release notes."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Once all project finish this, we will be able to deprecate it in Oslo policy"},{"line_number":66,"context_line":"also which allow policy deprecation without causing pain to OpenStack deployers."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f621f24_eface136","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":75},"in_reply_to":"1f621f24_8080bb8d","updated":"2020-11-02 16:38:17.000000000","message":"adding in https://review.opendev.org/#/c/760956/1","commit_id":"9a53610a57a7b8c29b27f42381d4e02f83234123"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"92a975fde44ec890482639114f8eb99f4b12b2e0","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"#. Change the default for config ``policy_file`` via ``set_defaults``."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"#. Deprecate the JSON format support via warnings in doc and release notes."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Once all project finish this, we will be able to deprecate it in Oslo policy"},{"line_number":66,"context_line":"also which allow policy deprecation without causing pain to OpenStack deployers."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f621f24_8080bb8d","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":75},"in_reply_to":"1f621f24_97764806","updated":"2020-10-30 13:07:39.000000000","message":"sure, I will push followup or initial example with reno and doc sample.\n\non JSON file keep working, it causes an issue when you deprecate the policy. And when cinder will do new policy (scope_type and reader role) then every policy rule will be deprecated with new policy.\n\nBut as you said, we will deprecate it for now and not sure when we can remove it removal is more critical and we should do when we are very sure every operator are using yaml.","commit_id":"9a53610a57a7b8c29b27f42381d4e02f83234123"}]}