)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":14250,"name":"Grzegorz Grasza","email":"xek@redhat.com","username":"xek"},"change_message_id":"bdc065b1cae877097a3411089d8ede4376682c0e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"3fa06805_2e50a750","updated":"2023-03-07 10:43:44.000000000","message":"LGTM!","commit_id":"60e6b7e64d7e9f750478b124c9e00718023861f7"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"eaccff332714e75a9388127d218df99ac7ebe247","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4229d0d5_13ce5346","updated":"2023-03-03 14:53:00.000000000","message":"lgtm","commit_id":"60e6b7e64d7e9f750478b124c9e00718023861f7"},{"author":{"_account_id":35125,"name":"Mauricio Harley","email":"mharley@redhat.com","username":"mharley-rh"},"change_message_id":"410ce4c50b2e0327b98823c1a5f8c88dc406a0bb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"fe407c17_a86a8e0e","updated":"2023-03-03 14:06:17.000000000","message":"recheck","commit_id":"60e6b7e64d7e9f750478b124c9e00718023861f7"}],"releasenotes/notes/secret-consumers-microversions-changes-5aacdad5b7c776a3.yaml":[{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"79acecc025858c337f92420661ee6e64e1b14dda","unresolved":true,"context_lines":[{"line_number":18,"context_line":"    user though.  When an end user needs to delete a secret that has"},{"line_number":19,"context_line":"    consumers, it can simply do it.  However, deletion of secrets with"},{"line_number":20,"context_line":"    consumers must be forced using a corresponding parameter, either"},{"line_number":21,"context_line":"    in the CLI or in the API."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    Microversions enable clients to do a server supported version"},{"line_number":24,"context_line":"    discovery, allowing old clients (not supporting the feature) to"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"b25c14f4_6e676c78","line":21,"range":{"start_line":21,"start_character":15,"end_line":21,"end_character":28},"updated":"2023-03-03 13:40:07.000000000","message":"IIRC, the Barbican API does not have a \"force\" parameter, only the client CLI and the client Python API?","commit_id":"6686e570eb2c1b6f04b5c5507f3e226d8f017c90"},{"author":{"_account_id":35125,"name":"Mauricio Harley","email":"mharley@redhat.com","username":"mharley-rh"},"change_message_id":"a0e6801fe5e7178c903a031ad5bab3fcd4edbd06","unresolved":false,"context_lines":[{"line_number":18,"context_line":"    user though.  When an end user needs to delete a secret that has"},{"line_number":19,"context_line":"    consumers, it can simply do it.  However, deletion of secrets with"},{"line_number":20,"context_line":"    consumers must be forced using a corresponding parameter, either"},{"line_number":21,"context_line":"    in the CLI or in the API."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    Microversions enable clients to do a server supported version"},{"line_number":24,"context_line":"    discovery, allowing old clients (not supporting the feature) to"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"8f525c27_c767baad","line":21,"range":{"start_line":21,"start_character":15,"end_line":21,"end_character":28},"in_reply_to":"b25c14f4_6e676c78","updated":"2023-03-03 13:51:44.000000000","message":"Done","commit_id":"6686e570eb2c1b6f04b5c5507f3e226d8f017c90"}]}