Azure Policy 模式：参数

Artículo
07/08/2024

可以将策略定义设置为动态，减少使用参数所需的策略定义的数量。参数在策略分配过程中定义。参数有一组预定义的属性，这些属性描述参数及其使用方式。

示例 1：字符串参数

此策略定义使用两个参数（tagName 和 tagValue）来设置策略分配在资源上查找的内容。此格式允许将策略定义用于任意数量的标记名称和标记值组合，但只保留单个策略定义。

注意

有关使用“全部”模式并与资源组配合使用的标签示例，请参阅模式：标签 - 示例 #1。

{
    "properties": {
        "displayName": "Require tag and its value",
        "policyType": "BuiltIn",
        "mode": "Indexed",
        "description": "Enforces a required tag and its value. Does not apply to resource groups.",
        "parameters": {
            "tagName": {
                "type": "String",
                "metadata": {
                    "description": "Name of the tag, such as costCenter"
                }
            },
            "tagValue": {
                "type": "String",
                "metadata": {
                    "description": "Value of the tag, such as headquarter"
                }
            }
        },
        "policyRule": {
            "if": {
                "not": {
                    "field": "[concat('tags[', parameters('tagName'), ']')]",
                    "equals": "[parameters('tagValue')]"
                }
            },
            "then": {
                "effect": "deny"
            }
        }
    }
}

示例 1：说明

"tagName": {
    "type": "String",
    "metadata": {
        "description": "Name of the tag, such as costCenter"
    }
},

在策略定义的此部分，我们将 tagName 参数定义为 string，并提供说明，方便其使用。

然后，我们在 policyRule.if 块中使用该参数，将策略设置为动态。在这里，它用于定义所计算的字段，该字段是值为 tagName 的标记。

"if": {
    "not": {
        "field": "[concat('tags[', parameters('tagName'), ']')]",
        "equals": "[parameters('tagValue')]"
    }
},

示例 2：数组参数

此策略定义使用单个参数 (listOfBandwidthinMbps)，目的是检查 Express Route 线路资源是否已将带宽设置配置为已批准的值之一。如果它不匹配，系统会拒绝创建或更新资源。

{
    "properties": {
        "displayName": "Allowed Express Route bandwidth",
        "description": "This policy enables you to specify a set of express route bandwidths that your organization can deploy.",
        "parameters": {
            "listOfBandwidthinMbps": {
                "type": "Array",
                "metadata": {
                    "description": "The list of SKUs that can be specified for express route.",
                    "displayName": "Allowed Bandwidth"
                }
            }
        },
        "policyRule": {
            "if": {
                "allOf": [{
                        "field": "type",
                        "equals": "Microsoft.Network/expressRouteCircuits"
                    },
                    {
                        "not": {
                            "field": "Microsoft.Network/expressRouteCircuits/serviceProvider.bandwidthInMbps",
                            "in": "[parameters('listOfBandwidthinMbps')]"
                        }
                    }
                ]
            },
            "then": {
                "effect": "Deny"
            }
        }
    }
}

示例 2：说明

"listOfBandwidthinMbps": {
    "type": "Array",
    "metadata": {
        "description": "The list of SKUs that can be specified for express route.",
        "displayName": "Allowed Bandwidth"
    }
}

在策略定义的此部分，我们将 listOfBandwidthinMbps 参数定义为 array，并提供说明，方便其使用。作为 array，它有多个要匹配的值。

然后，我们在 policyRule.if 块中使用该参数。作为 array 参数，必须使用 array条件的 in 或 notIn。在这里，我们将其用于 serviceProvider.bandwidthInMbps 别名，作为定义的值之一。

"not": {
    "field": "Microsoft.Network/expressRouteCircuits/serviceProvider.bandwidthInMbps",
    "in": "[parameters('listOfBandwidthinMbps')]"
}

示例 3：参数化效果

使策略定义可重复使用的一种常见方法是参数化效果本身。本示例使用单个参数“effect”。通过参数化效果，可以将相同的定义分配给具有不同效果的不同作用域。

{
    "properties": {
        "displayName": "All authorization rules except RootManageSharedAccessKey should be removed from Service Bus namespace",
        "policyType": "BuiltIn",
        "mode": "All",
        "description": "Service Bus clients should not use a namespace level access policy that provides access to all queues and topics in a namespace. To align with the least privilege security model, you should create access policies at the entity level for queues and topics to provide access to only the specific entity",
        "metadata": {
            "version": "1.0.1",
            "category": "Service Bus"
        },
        "parameters": {
            "effect": {
                "type": "string",
                "defaultValue": "Audit",
                "allowedValues": [
                    "Audit",
                    "Deny",
                    "Disabled"
                ],
                "metadata": {
                    "displayName": "Effect",
                    "description": "The effect determines what happens when the policy rule is evaluated to match"
                }
            }
        },
        "policyRule": {
            "if": {
                "allOf": [{
                        "field": "type",
                        "equals": "Microsoft.ServiceBus/namespaces/authorizationRules"
                    },
                    {
                        "field": "name",
                        "notEquals": "RootManageSharedAccessKey"
                    }
                ]
            },
            "then": {
                "effect": "[parameters('effect')]"
            }
        }
    }
}

示例 3：说明

"parameters": {
    "effect": {
        "type": "string",
        "defaultValue": "Audit",
        "allowedValues": [
            "Audit",
            "Deny",
            "Disabled"
        ],
        "metadata": {
            "displayName": "Effect",
            "description": "The effect determines what happens when the policy rule is evaluated to match"
        }
    }
},

在策略定义的此部分中，将“effect”参数定义为“string”。策略定义将分配的默认值设置为“audit”，并将其他选项限制为“disabled”和“deny”。

然后在 policyRule.then 块中将参数用于“effect”。

"then": {
    "effect": "[parameters('effect')]"
}

Compartir a través de