Skip to content

Commit 1c573e9

Browse files
committed
fixes
1 parent 995ad07 commit 1c573e9

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

docs/build-your-software-catalog/customize-integrations/configure-data-model/setup-blueprint/properties/aggregation-property.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -969,7 +969,7 @@ Count how many deployments are directly related to a cluster:
969969
"target": "deployment",
970970
"pathFilter": [
971971
{
972-
"path": ["deployment_rel"]
972+
"path": ["deployments_rel"]
973973
}
974974
],
975975
"calculationSpec": {
@@ -981,7 +981,7 @@ Count how many deployments are directly related to a cluster:
981981
}
982982
```
983983

984-
The `pathFilter` with `"path": ["deployment_rel"]` counts deployments that are directly related to the cluster through the `deployment_rel` relation.
984+
The `pathFilter` with `"path": ["deployments_rel"]` counts deployments that are directly related to the cluster through the `deployments_rel` relation.
985985

986986
<h4>Example 2: Using fromBlueprint</h4>
987987

@@ -997,8 +997,8 @@ Count how many clusters are related to a deployment:
997997
"target": "cluster",
998998
"pathFilter": [
999999
{
1000-
"path": ["deployment_rel"],
1001-
"fromBlueprint": "deployment"
1000+
"path": ["deployments_rel"],
1001+
"fromBlueprint": "cluster"
10021002
}
10031003
],
10041004
"calculationSpec": {
@@ -1010,7 +1010,7 @@ Count how many clusters are related to a deployment:
10101010
}
10111011
```
10121012

1013-
The `fromBlueprint: "deployment"` specifies that the path traversal should start from the deployment blueprint (the target), then follow the path backwards through `deployment_rel` to cluster.
1013+
The `fromBlueprint: "cluster"` specifies that the path traversal should start from the cluster blueprint (the target), then follow the path backwards through `deployments_rel` to deployment.
10141014

10151015
</TabItem>
10161016

@@ -1041,7 +1041,7 @@ resource "port_aggregation_properties" "cluster_aggregation_properties" {
10411041
description = "Deployment Count"
10421042
path_filter = [
10431043
{
1044-
path = ["deployment_rel"]
1044+
path = ["deployments_rel"]
10451045
}
10461046
]
10471047
method = {
@@ -1052,7 +1052,7 @@ resource "port_aggregation_properties" "cluster_aggregation_properties" {
10521052
}
10531053
```
10541054

1055-
The `path = ["deployment_rel"]` counts deployments that are directly related to the cluster through the `deployment_rel` relation.
1055+
The `path = ["deployments_rel"]` counts deployments that are directly related to the cluster through the `deployments_rel` relation.
10561056

10571057
<h4>Example 2: Using fromBlueprint</h4>
10581058

@@ -1079,8 +1079,8 @@ resource "port_aggregation_properties" "deployment_aggregation_properties" {
10791079
description = "Cluster Count"
10801080
path_filter = [
10811081
{
1082-
path = ["deployment_rel"]
1083-
from_blueprint = "deployment"
1082+
path = ["deployments_rel"]
1083+
from_blueprint = "cluster"
10841084
}
10851085
]
10861086
method = {
@@ -1091,7 +1091,7 @@ resource "port_aggregation_properties" "deployment_aggregation_properties" {
10911091
}
10921092
```
10931093

1094-
The `from_blueprint = "deployment"` specifies that the path traversal should start from the deployment blueprint (the target), then follow the path backwards through `deployment_rel` to cluster.
1094+
The `from_blueprint = "cluster"` specifies that the path traversal should start from the cluster blueprint (the target), then follow the path backwards through `deployments_rel` to deployment.
10951095

10961096
</TabItem>
10971097

7.52 KB
Loading

0 commit comments

Comments
 (0)