6f8837d84e
Allow operators to specify different policies for each action, since each action is quite different in character. The previous "actions:action" rule remains and is the default for each of the new rules, so there is no effect on existing policies and no action required by the operator unless they want to take advantage of the additional flexibility. Change-Id: Ic4985e8637bc4f34ea2514075b30d2ec32f3441c Task: 37296
11 lines
520 B
YAML
11 lines
520 B
YAML
---
|
|
features:
|
|
- |
|
|
Operators can now apply different authorization policies to each action
|
|
supported by the action API (``actions:suspend`` for suspend,
|
|
``actions:resume`` for resume, ``actions:check`` for check,
|
|
``actions:cancel_update`` for cancel operation and roll back, and
|
|
``actions:cancel_without_rollback`` for cancel operation without rolling
|
|
back). The default for each is to use the existing ``actions:action`` rule
|
|
that was previously the only way to specify policy for actions.
|