Skip to content

[Task]: Allow policy violations to execute follow-up delayed blocks actions on top of the negative action for the entity #16120

@diox

Description

@diox

Description

CinderPolicy allows several enforcement_actions to be set, but currently we only support one decision and one action per entity at execution time.

We need the ability to set the new delayed block actions from #16119 as additional enforcement actions for any policy. Those would still be configured as enforcement_actions but could be special-cased for now so that they are never going to be executed on their own, and always as follow-up for another negative action. Successful appeals would automatically unblock as part of #16119

Implementation note: the ideal future end-state would be allowing a policy violation to either execute multiple decisions with a single action, or allowing a single decision to have multiple actions. For now however, as noted above the only requirement is the ability to execute delayed hard or soft block actions after a negative action, so we can add hacks as necessary.

Acceptance Criteria

  • item 1

┆Issue is synchronized with this Jira Task

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions