Repository navigation
Parsing json with unnamed array #1131
|
I am trying to do PSRule validation on below json file, which is having an unnamed array with 3 elements. I am looking to fetch the value of field 'RoleDefinitionName' of the first element only and validate its value. I tried using this expression but its returning me value from all three child elements. How can we handle this unnamed array for fetching a particular value. Any help or suggestion would be highly appreciated. Thankyou. $ActualValue = $TargetObject.RoleDefinitionName
[ |
Replies: 2 comments 3 replies
|
EY Ankur (@ankur90Git) By default rules run against all input objects, however you can use conditions to limit which objects that apply to by configuring a pre-condition. When set, rules will only apply to objects that return For a single rule, the easiest way would be to use a script pre-condition, like this: # Synopsis: An example script rule with pre-conditions.
Rule 'AppConfigurationPermission' -If { $TargetObject.RoleDefinitionName -eq 'App Configuration Data Reader' } {
# Rule condition
}While the other objects would still be discovered, the rule will only run against the first object. Which is probably what you want because there may be other rules for the other objects. You can disable the warning generated for objects not matching any rules by setting Execution.NotProcessedWarning. There are some more detail here: Using pre-conditions I hope that helps. |
|
Thankyou so much for answering my question. Your answer helped me in solving my problem. |
|
EY Ankur (@ankur90Git) No worries. When PSRule is the run with the See Input.Format. This means that if the |
|
@BernieWhite ok thanks. One last question, for such json(having array at the root) any option which we can use so that PS Rule considers it as 1 input only and not 3? Because I have all the input json of this format only and creating rule conditions for such input is getting bit complex. Appreciate your response. |
|
EY Ankur (@ankur90Git) There isn't an easy way to do this by default, but it could be done with a convention. Although maybe binding, selectors, or helper functions make address the concerns. Writing a convention, you can add this is a separate # Synopsis: Create .JSON file and import whole array object.
Export-PSRuleConvention 'ExportArray' -If { $TargetObject -is [PSRule.Data.InputFileInfo] -and $TargetObject.Extension -eq '.json' } -Begin {
$json = Get-Content -Path $TargetObject.FullName -Raw | ConvertTo-Json;
$PSRule.Import($json);
}You would then reference it from you command-line. Invoke-Psrule -InputPath .\example.json -Path .\.ps-rule\ -Format File -Convention ExportArrayEach file would be found then imported. Outside of that maybe you can explain your use case in feature request if none of these options work. Thanks. |
EY Ankur (@ankur90Git) By default rules run against all input objects, however you can use conditions to limit which objects that apply to by configuring a pre-condition. When set, rules will only apply to objects that return
$truefor the pre-condition.For a single rule, the easiest way would be to use a script pre-condition, like this:
While the other objects would still be discovered, the rule will only run against the first object. Which is probably what you want because there may be other rules…