Closed MikaelJcSoderberg closed 3 months ago
@Springstone can you take a look at this one please buddy?
The allowed parameters are indeed incorrect but should not be an issue if you use Deny
. To address this issue, we have a PR in to address the correct allowed parameters.
Have a PR in #1702 that fixes this and ensure built-in policy alignment for parameters.
Describe the bug There are wrong values for this parameter : modifyNsgRuleAccess
"modifyNsgRuleAccess": { "type": "string", "defaultValue": "Deny", "allowedValues": [ "Audit", "Deny", "Disabled" ] }
It should be
"modifyNsgRuleAccess": { "type": "string", "defaultValue": "Deny" "allowedValues": [ "Allow", "Deny" ] }
Steps to reproduce Assign Enforce-Guardrails-NetworkScreenshots