You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Complex identifier using search query to find entity by ARN
115
+
identifier = jsonencode({
116
+
combinator = "'and'",
117
+
rules = [
118
+
{
119
+
property = "'arn'"
120
+
operator = "'='"
121
+
value = ".body.resources[0]"
122
+
}
123
+
]
124
+
})
125
+
title = ".body.repository.name"
126
+
properties = {
127
+
url = ".body.repository.html_url"
128
+
}
129
+
}
130
+
}
131
+
]
132
+
133
+
depends_on = [
134
+
port_blueprint.microservice
135
+
]
136
+
101
137
}
102
138
```
103
139
Notes
104
-
When using object format for relations, combinator, property and operator fields should be enclosed in single quotes, while value should not have quotes as it's a JQ expression. The single quotes are required because these fields contain literal string values that must be passed as-is to the Port API, whereas value contains a JQ expression that should be evaluated dynamically.For all available operators, see the Port comparison operators documentation https://docs.port.io/search-and-query/comparison-operators.
140
+
When using object format for relations, combinator, property and operator fields should be enclosed in single quotes, while value should not have quotes as it's a JQ expression. The single quotes are required because these fields contain literal string values that must be passed as-is to the Port API, whereas value contains a JQ expression that should be evaluated dynamically.The identifier field supports both simple JQ expressions (strings) and complex search query objects. When using search query objects, the structure must include combinator and rules fields, and each rule must have property, operator, and value fields.For all available operators, see the Port comparison operators documentation https://docs.port.io/search-and-query/comparison-operators.
# Complex identifier using search query to find entity by ARN
261
+
identifier = jsonencode({
262
+
combinator = "'and'",
263
+
rules = [
264
+
{
265
+
property = "'arn'"
266
+
operator = "'='"
267
+
value = ".body.resources[0]"
268
+
}
269
+
]
270
+
})
271
+
title = ".body.repository.name"
272
+
properties = {
273
+
url = ".body.repository.html_url"
274
+
}
275
+
}
276
+
}
277
+
]
278
+
279
+
depends_on = [
280
+
port_blueprint.microservice
281
+
]
282
+
}
283
+
211
284
```
212
285
213
286
## Notes
214
287
215
288
- When using object format for relations, `combinator`, `property` and `operator` fields should be enclosed in single quotes, while `value` should not have quotes as it's a JQ expression. The single quotes are required because these fields contain literal string values that must be passed as-is to the Port API, whereas `value` contains a JQ expression that should be evaluated dynamically.
289
+
- The `identifier` field supports both simple JQ expressions (strings) and complex search query objects. When using search query objects, the structure must include `combinator` and `rules` fields, and each rule must have `property`, `operator`, and `value` fields.
216
290
- For all available operators, see the [Port comparison operators documentation](https://docs.port.io/search-and-query/comparison-operators).
217
291
218
292
@@ -259,7 +333,7 @@ Optional:
259
333
260
334
Required:
261
335
262
-
-`identifier` (String) The identifier of the entity
336
+
-`identifier` (String) The identifier of the entity. Can be either a simple JQ expression (string) or a search query object encoded with jsonencode(). When using search query objects, the structure must include 'combinator' and 'rules' fields, and each rule must have 'property', 'operator', and 'value' fields.
0 commit comments