-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to apply policies to microflows #5
Labels
Comments
The current approach is: Convert the directed cyclic graph to a directed acyclic graph. Whenever we encounter a merge, we will do a backtrack walk to check if it is cycle. If it is, we stop at the merge, mark it as a loop. This loop is then recorded as such in the list of loops. |
Merged
Closed by accident. Basic has been implemented; but we still want to have looping :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use case
We would like to be able to implement policies that checks anatomy of microflow implementations. Like avoid commit inside of a loop.
Solution
translate the flows into nested dictionaries. Dictionaries (objects) and lists can be processed easily by OPA. If we convert to some human-readable pseudo code, OPA might not be able to parse it efficiently.
The text was updated successfully, but these errors were encountered: