So API should not only configure policy but also have understanding position and pipeline name.
That is not the end. Policy contains condition\action pairs that need to be managed
p2: [
cond1/action1
cond2/action2
]
OUT of scope:
both of them have some schema to validate. (because it will make changes to plugin framework and introduce validation engine in the API, this could be 2 additional stories)
apiPipeline
So API should not only configure policy but also have understanding position and pipeline name.
That is not the end. Policy contains condition\action pairs that need to be managed p2: [
OUT of scope: both of them have some schema to validate. (because it will make changes to plugin framework and introduce validation engine in the API, this could be 2 additional stories)