| 1 |
--- |
| 2 |
features: |
| 3 |
- The ``force`` boolean parameter has been added to the volume |
| 4 |
delete API. It may be used in combination with ``cascade``. |
| 5 |
This also means that volume force delete is available |
| 6 |
in the base volume API rather than only in the |
| 7 |
``volume_admin_actions`` extension. |
| 8 |
upgrade: |
| 9 |
- There is a new policy option ``volume:force_delete`` which |
| 10 |
controls access to the ability to specify force delete |
| 11 |
via the volume delete API. This is separate from the |
| 12 |
pre-existing ``volume-admin-actions:force_delete`` policy |
| 13 |
check. |