...
| Code Block | ||
|---|---|---|
| ||
{
"policies": [
{
"policy-id": "operational.sampleusecase1",
"policy-version": 1,
"dependencies": [
{
"groupId": "org.onap.policy.sampledomain",
"artifactId": "policy-sample-usecase1",
"version": "1.0.0-SNAPSHOT"
}
],
"controller": {
"name": "sample-usecase1",
"config_body": "<config body>"
}
},
{
"policy-id": "operational.sampleusecase2",
"dependencies": [
{
"groupId": "org.onap.policy.sampledomain",
"artifactId": "policy-sample-usecase2",
"version": "1.0.0-SNAPSHOT"
}
],
"controller": {
"name": "sample-usecase2",
"config_body": "<config body>"
}
}
]
} |
Flow explanation
TBAThe flow will be almost the same as in option 1. The only difference is, PAP will not only send policy and its type implementation but also peripheral configs to PDP as those configs come from deployment API payload instead of embedded in policy type implementation.
Sequence diagram
