Bernie White

@ArmaanMcleod Let's go with option 2. It adds complexity to manage merging nested objects. If we don't need to better to keep it simple.

@jagoodwin Ok awesome. We can focus on adding rules for these. Then we can look at others as they come up.

> Logs show a WARNING: Target object 'modules/Microsoft.Resources/resourceGroups/.test/common/deploy.test.bicep' has not been processed because no matching rules were found. although the file is then checked successfully Currently this is by design,...

> PSRule VSC extension: cannot be used due to tokenized parameters. Interested in finding more about this one.

> [SuppressionGroups](https://microsoft.github.io/PSRule/v2/concepts/PSRule/en-US/about_PSRule_SuppressionGroups/) do not allow the use of wildcards for rule names Example: skip Azure.KeyVault.* Interested in more detail about this or a feature request.

@ArmaanMcleod Can we write. # Example 1 Policy example: ```json { "count": { "field": "Microsoft.Network/networkSecurityGroups/securityRules[*]" }, "equals": 0 } ``` PSRule example: ```yaml field: properties.securityRules[*] count: 0 ``` # Example...

@ArmaanMcleod It think it is still worth leaving open to make sure we cover it in complex expressions. The first pass of #1045 may not provide all the final features...

@ArmaanMcleod Good question. The `..` descendant operator is not supported but the grouping should work. We don't specifically have a test case for it, but ideally it should work if...

@ArmaanMcleod That's how I'd do it. Does it work? I don't think we specifically have a test case for that but maybe worth adding any of these to tests at...

Sub-selectors and functions as they move forward should address the remaining points that are hard to do with YAML and JSON expressions.