Ability to use several combinators
M
Max Timoshchenko
Additional filters of widgets allow to set only one combinator.
Example:
{
"combinator": "and",
"rules": [
{
"property": "argocdAppName",
"operator": "contains",
"value": "staging3"
},
{
"operator": "=",
"value": "argocdApplication",
"property": "$blueprint"
}
]
}
it would be good to have the ability to write more complex conditions. combine AND and OR combinators
Guy Berman
Hi Max Timoshchenko, Jordan Lang,
Thanks for the suggestion!
This is actually already supported at the JSON level in the permissions configuration, it’s just not yet available through the UI.
You can define multiple combinators directly in the permissions JSON. For example:
{
"combinator": "and",
"rules": [
{
"combinator": "or",
"rules": [
{
"operator": "=",
"property": "property1",
"value": "value1"
},
{
"operator": "=",
"property": "property2",
"value": "value2"
}
]
}
]
}
This allows you to nest combinators and build more advanced logical conditions today.
We agree that this should be supported directly in the UI as well, and it’s something we’d like to add in the future to make it easier to configure without editing JSON manually.
Thanks again for raising this!
J
Jordan Lang
To expand on this feature request, blueprint read permission policies need support for nested combinators. Currently, policies are limited to using either "and" OR "or" at the top level, which significantly restricts their usefulness for real-world access control scenarios.
Many common use cases require mixed logic like (Team Access AND Resource Criteria) OR Territory Access.
Adding this capability would greatly enhance the practical value of Port's blueprint-level permissions.