Skip to content

Commit 355b117

Browse files
authored
Merge pull request #127731 from rfernandezdo/patch-5
Update documentation for wildcard usage in conditions
2 parents 2db7edb + 7d8d29d commit 355b117

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

articles/governance/policy/concepts/definition-structure-policy-rule.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,8 @@ A condition evaluates whether a value meets certain criteria. The supported cond
8282

8383
For `less`, `lessOrEquals`, `greater`, and `greaterOrEquals`, if the property type doesn't match the condition type, an error is thrown. String comparisons are made using `InvariantCultureIgnoreCase`.
8484

85+
When using the `contains` and `notContains` conditions, the wildcard character (`*`) cannot be provided in the value.
86+
8587
When using the `like` and `notLike` conditions, you provide a wildcard character (`*`) in the value. The value shouldn't have more than one wildcard character.
8688

8789
When using the `match` and `notMatch` conditions, provide a hashtag (`#`) to match a digit, question mark (`?`) for a letter, and a dot (`.`) to match any character, and any other character to match that actual character. While `match` and `notMatch` are case-sensitive, all other conditions that evaluate a `stringValue` are case-insensitive. Case-insensitive alternatives are available in `matchInsensitively` and `notMatchInsensitively`.

0 commit comments

Comments
 (0)