congress

Policy engine triggers

Registered by Tim Hinrichs

Currently there is no mechanism for treating changes to
policy-defined tables as events (aka triggers). Treating changes to
policy-defined tables as events is useful because
it enables us to, for example,
(i) publish those changes on the message bus
(ii) set up reactive enforcement, either written in code or
in policy,
(iii) kicking off translations to other policy
engines.

Blueprint information

Status:
Complete
Approver:
Aaron Rosen
Priority:
High
Drafter:
Tim Hinrichs
Direction:
Approved
Assignee:
Zhenzan Zhou
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon kilo-3
Started by
Tim Hinrichs
Completed by
Tim Hinrichs

Related branches

Sprints

Whiteboard

Does this bp has some dependency to others like https://review.openstack.org/#/q/status:open+project:stackforge/congress-specs+branch:master+topic:reactive-enforcement,n,z ? If so, I think it would be nice to mark the dependency here too. :)

I added the dependency graph info. Good suggestion!

Addressed by: https://review.openstack.org/163645
    Add triggers to domain-agnostic policy engine

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.