Support for additional logical operators in conditional execution
P
Plum Gerbil
In our project, we need to write conditions that can compare hostnames and skip deployment on certain hosts. Currently, we do not have support for logical operators like 'not in,' 'between,' or 'contains' to make the conditions more robust. It would be very helpful if these additional logical operators could be supported in the future.
Log In
Canny AI
Merged in a post:
Feature Request
S
Sensible Macaw
Hello, I am asking for a feature request when creating cost bucket logic. Currently when when creating the logic there is a "Like" operator. I am requesting a "Not Like" operator. The current use case is that in UWM they have 1,000+ azure resource groups that are constantly updated with snapshots of other resources that they are attached to. This bleeds over into some of the other cost buckets that are currently build. We would like to build the logic to read " An Azure resource group name is NOT LIKE *****" This would exclude these 1000+ resource groups in one line.