Adding accessPolicies to existing keyVault results in error validating property "name"

[SimonWahlin]

Bicep version
Bicep CLI version 0.1.226-alpha (eb3d221)

Describe the bug
Trying to add an accessPolicy to existing keyvault using the name '${keyVault.name}/add'

This results in following error message when trying to build:

Error BCP036: The property "name" expected a value of type "'add' | 'remove' | 'replace'" but the provided value is of type "string".

The property name should be KeyVaultName/add, but bicep validates the whole name against the valid names add/remove/replace instead of just the child-part of the name.

To Reproduce
Add an accessPolicy to existing key vault with following bicep code:

resource keyVaultAccessPolicy 'Microsoft.KeyVault/vaults/accessPolicies@2019-09-01' = {
    name: '${keyVault.name}/add'
    properties: {
        accessPolicies: [
            {
                tenantId: functionApp.outputs.principalTenantId
                objectId: functionApp.outputs.principalId
                permissions: {
                    certificates: [
                        'get'
                        'list'
                        'create'
                        'update'
                    ]
                }
            }
        ]
    }
}

Where keyVault is a Key Vault I just created in the same bicep file and functionApp is a nested deployment that deploys a functionApp with a managed identity.

Additional context
Seems like this is related to the discussion about introducing a parent syntax in #657

[alex-frankel]

thanks for reporting

this is a bug we'll need to fix, but in the meantime you can unblock yourself with the any() function:

resource keyVaultAccessPolicy 'Microsoft.KeyVault/vaults/accessPolicies@2019-09-01' = {
    name: any('${keyVault.name}/add')
    ...
}

[SimonWahlin]

Thanks @alex-frankel, your workaround worked like a charm as always!

[alex-frankel]

@anthony-c-martin - will this be solved by #657? Or is this a KV swagger issue?

[anthony-c-martin]

The swagger looks correct - #657 will fix it this.

[anthony-c-martin]

Fixed with #657