openstack
/
nova-specs
Code Issues Proposed changes

Suggest when to propose notification changes 

This patch adds couple of cases when the spec author should consider
proposing changes to the versioned notification related to the proposed
feature.

Change-Id: Ide0b58003aee46bd41f4df4e52503e415cbfc04b
This commit is contained in:
Balazs Gibizer 2018-04-18 14:41:09 +02:00
parent dad9782fc1
commit fedf55f735
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
specs/rocky-template.rst
View File

@ -222,6 +222,18 @@ Notifications impact
Please specify any changes to notifications. Be that an extra notification,
changes to an existing notification, or removing a notification.
Consider proposing changes to the versioned notifications:
* When the feature adds or removes fields to the API responses. For example
when the feature adds a new field to the ``GET /servers`` API response
consider adding similar information to the payload of the instance action
notifications
* When the feature adds a new action to the existing API entities. For example
adding a new action to the server might mean you want to emit a corresponding
new instance action notification
* When the feature adds a new resource (noun) to the REST API consider adding
new notifications about the creation and deletion of such resource
Other end user impact
---------------------