)]}'
{"releasenotes/notes/granular-action-policy-b8c143bb5f203b68.yaml":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"f629cf9011452b59bc4ccc3b19638a0719355e41","unresolved":false,"context_lines":[{"line_number":4,"context_line":"    Operators can now apply different authorization policies to each action"},{"line_number":5,"context_line":"    (suspend, resume, check, cancel operation and roll back, cancel operation"},{"line_number":6,"context_line":"    without rolling back) supported by the action API. Previously all were"},{"line_number":7,"context_line":"    controlled by a single ``actions:action`` policy."},{"line_number":8,"context_line":"deprecations:"},{"line_number":9,"context_line":"  - |"},{"line_number":10,"context_line":"    The ``actions:action`` policy is deprecated in favor of more granular"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3fa7e38b_e0d8f052","line":7,"updated":"2019-10-28 13:25:08.000000000","message":"nit:\n\nWhen we made changes like this in keystone, we documented the policy names and check strings in the release note [0].\n\nIt\u0027s verbose, but it prevents operators from having to dig into the source code or generate sample policy files to figure out what the new policy is.\n\n[0] https://docs.openstack.org/releasenotes/keystone/train.html#deprecation-notes","commit_id":"8b9bd07cab6c3b8ae27439518aa289a1e5d4c6ee"}]}