)]}'
{"doc/source/reference/notifications.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"54be7a10741b767d2e17be942d4f27c17e92eba1","unresolved":false,"context_lines":[{"line_number":334,"context_line":"  notification payload. This way the evolution of the internal object model"},{"line_number":335,"context_line":"  can be decoupled from the evolution of the notification payload."},{"line_number":336,"context_line":""},{"line_number":337,"context_line":"  .. important:: This does not mean that every field from internal objects"},{"line_number":338,"context_line":"                 should be mirrored in the notification payload objects."},{"line_number":339,"context_line":"                 Think about what is actually needed by a consumer before"},{"line_number":340,"context_line":"                 adding it to a payload. When in doubt, if no one is requesting"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_5c2d60a6","line":337,"updated":"2019-04-04 16:57:42.000000000","message":"Surya brought up a good question here:\n\nhttps://review.openstack.org/#/c/614035/\n\nEssentially do we have any rules about when to mirror fields in the notifications. In the case of that change, it\u0027s all internal so I say we don\u0027t need to mirror it until someone specifically requests it. But for her locked_by/locked_reason spec:\n\nhttps://review.openstack.org/#/c/638629/\n\nThat\u0027s a bit different because the Searchlight team in the past asked us to mirror fields in the REST API into the versioned notifications as well, so maybe that is worth documenting in a follow up.","commit_id":"88560094450bb4935909793965866b542d9ef3fe"}]}