| 1 |
--- |
| 2 |
deprecations: |
| 3 |
- | |
| 4 |
In this release, sending ``os-reset_status`` notifications to the |
| 5 |
following *nonstandard* publisher_ids is DEPRECATED: |
| 6 |
|
| 7 |
* 'volumeStatusUpdate' for volume status resets |
| 8 |
* 'volumeStatusUpdate' for snapshot status resets |
| 9 |
* 'backupStatusUpdate' for backup status resets |
| 10 |
|
| 11 |
The notifications continue to be published to the above during the |
| 12 |
deprecation period. Beginning with this release, the ``os-reset_status`` |
| 13 |
notifications are also sent to the following *standard* publisher_ids: |
| 14 |
|
| 15 |
* 'volume' for volume status resets |
| 16 |
* 'snapshot' for snapshot status resets |
| 17 |
* 'backup' for backup status resets |
| 18 |
|
| 19 |
This will allow consumers of these notifications to make a smooth |
| 20 |
transition. In the Victoria release, ``os-reset_status`` notifications |
| 21 |
will *only* be sent to the standard publisher_ids. |
| 22 |
fixes: |
| 23 |
- | |
| 24 |
``os-reset_status`` notifications for volumes, snapshots and backups will |
| 25 |
now go to the standard publisher id for volume, snapshot and backup like |
| 26 |
all other notifications for volume, snapshot and backup. |