Relationship Selector Example
"selectors": [
{
"allow": {
"from": [
{
"kind": "WASMFilter",
"model": { "name": "meshery-core" },
"patch": {
"patchStrategy": "replace",
"mutatorRef": [
["configuration", "config"]
]
}
}
],
"to": [
{
"kind": "EnvoyFilter",
"model": { "name": "istio-base" },
"patch": {
"patchStrategy": "replace",
"mutatedRef": [
["configuration", "spec", "configPatches", "_", "patch", "value"]
]
}
}
]
},
"deny": {
"from": [],
"to": []
}
},
{
"allow": {
"from": [
{
"kind": "ConfigMap",
"model": { "name": "kubernetes" },
"patch": {
"patchStrategy": "replace",
"mutatorRef": [
["configuration", "metadata", "name"]
]
}
}
],
"to": [
{
"kind": "Deployment",
"model": { "name": "kubernetes" },
"patch": {
"patchStrategy": "replace",
"mutatedRef": [
["configuration", "spec", "template", "spec", "containers", "_", "envFrom", "0", "configMapRef", "name"]
]
}
}
]
},
"deny": {
"from": [],
"to": []
}
}
]
The first selector-set item (WASMFilter → EnvoyFilter) is independent of the second (ConfigMap → Deployment). Use separate items when the pairs should not cross-match.
The WASMFilter example is hierarchical parent **wallet** (child config patched into the parent). The ConfigMap example is edge **reference** (a name pointer), not hierarchical inventory.
#### Understanding Relationship Policies and their Evaluation
Meshery evaluates designs with Open Policy Agent. The engine enters through the fixed policy package `data.relationship_evaluation_policy` and dispatches on each definition's `kind`, `type`, and `subType`. The policies live under `models/meshery-core/
