Misplacement of schema in AllowedHostPathVolumesInKubernetesClusterList Policy Parameter?

[arodindev]

Details of the scenario you tried and the problem that is occurring

In the Microsoft Cloud Security Benchmark, the policy parameter AllowedHostPathVolumesInKubernetesClusterList defines a schema object nested under metadata. Is this placement intentional, or should the schema be defined at the top level of the parameter?

https://github.com/Azure/azure-policy/blob/master/built-in-policies/policySetDefinitions/Azure%20Government/Security%20Center/AzureSecurityCenter.json#L4137

Verbose logs showing the problem

Suggested solution to the issue

Define the schema at the top level of the parameter alongside type, defaultValue, etc.?

If policy is Guest Configuration - details about target node