ARM Template locks

Open
#444 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure
Domain
cloud

Research direction

Start by reviewing the ARM template examples in the issue and the Microsoft.Authorization/locks resource scope shown there. Determine whether key-value locking belongs in the key-value properties, resource-lock support, or both. Done means the supported creation and post-creation locking behavior is documented and validated for the requested scenarios.

Written by the indexing model from the issue text.

Description

ARM enhancement

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."
    }
},
Dominant language
No language data
Stars
263
Forks
82
Avg merge
3d 15h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AppConfiguration

All issues in Azure/AppConfiguration

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.