Based on bug 1823104 it's clear we should have some
explicit wording in the notification reference docs
about what not to include in versioned notification
payloads, so this change attempts to start that with
the most obvious thing - don't expose access credentials
to the nova deployment.
This also adds a reminder to think about what is being
added / mirrored from internal objects and determine if
consumers really need it and if they aren't asking, opt
to not including it until requested.
Reviewed: https:/ /review. openstack. org/650020 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=88560094450 bb4935909793965 866b542d9ef3fe
Committed: https:/
Submitter: Zuul
Branch: master
commit 88560094450bb49 35909793965866b 542d9ef3fe
Author: Matt Riedemann <email address hidden>
Date: Thu Apr 4 10:20:32 2019 -0400
Add docs on what not to include in notifications
Based on bug 1823104 it's clear we should have some
explicit wording in the notification reference docs
about what not to include in versioned notification
payloads, so this change attempts to start that with
the most obvious thing - don't expose access credentials
to the nova deployment.
This also adds a reminder to think about what is being
added / mirrored from internal objects and determine if
consumers really need it and if they aren't asking, opt
to not including it until requested.
Change-Id: I326aa39d963091 282a5d0b70ba222 abfe8ccfdac
Related-Bug: #1823104