ARM Template locks

[mattboothman]

I'd like the ability to lock a keyvalue at creation and/or after creation.

Perhaps something like this (see .properties.locked):

{
    "type": "Microsoft.AppConfiguration/configurationStores/keyValues",
    "apiVersion": "2020-07-01-preview",
    "name": "[concat(variables('configStoreName'), '/environment:name')]",
    "dependsOn": [
        "[variables('configStoreName')]"
    ],
    "properties": {
        "value": "[parameters('environmentName')]",
        "contentType": "text/plain",
        "tags": "",
        "locked": true
    }
},

The alternative is that I'm able to apply resource locks to configuration keyvalues, but this would also be useful in addition to the above method.

{
    "type": "Microsoft.Authorization/locks",
    "apiVersion": "2016-09-01",
    "name": "environmentNameLock",
    "scope": "[resourceId('Microsoft.AppConfiguration/configurationStores/keyValues', variables('configStoreName'), 'environment:name')]",
    "dependsOn": [
        "[resourceId('Microsoft.AppConfiguration/configurationStores/keyValues', variables('configStoreName'), 'environment:name')]"
    ],
    "properties": {
        "level": "ReadOnly",
        "notes": "Config must not be modified or deleted."
    }
},

[recao]

Hi @mattboothman

The ability to lock KV through ARM templates is not on our roadmap at this point, since we have not received this feature request from customers yet. As we are actively working on new features, this would be put into consideration for future designs. Thanks.

[mattboothman]

Hey @recao I’m a customer actively using the product, requesting the feature.

[recao]

@mattboothman yes, and we always try our best to fulfill every customer's request based on our development capacity, feature priority and existing roadmap.

Add @zhenlan and @drago-draganov