The work planned to move the OpenStack actions to mistral-extra [1] will solve this problem with OpenStack actions.
There is currently no plan to allow disabling any of the std.* actions, but I agree it would be useful in some cases.
There is another blueprint for Action Providers [2]. If this work is done then the action providers could support configuration and a action provider could be used to represent the std.* actions. This would then allow enabling and disabling and of the actions in that provider.
It is likely that the action providers need to be implemented for the openstack actions in mistral-extra to be feasible.
The work planned to move the OpenStack actions to mistral-extra [1] will solve this problem with OpenStack actions.
There is currently no plan to allow disabling any of the std.* actions, but I agree it would be useful in some cases.
There is another blueprint for Action Providers [2]. If this work is done then the action providers could support configuration and a action provider could be used to represent the std.* actions. This would then allow enabling and disabling and of the actions in that provider.
It is likely that the action providers need to be implemented for the openstack actions in mistral-extra to be feasible.
[1]: https:/ /blueprints. launchpad. net/mistral/ +spec/mistral- actions- api-separate- openstack- actions /blueprints. launchpad. net/mistral/ +spec/mistral- action- providers
[2]: https:/