Open MattacksWTW opened 2 years ago
If it's any of help, we are using this approach:
new AzureNative.AppConfiguration.KeyValueArgs {
ContentType = "application/vnd.microsoft.appconfig.keyvaultref+json;charset=utf-8",
ConfigStoreName = <app_config_name>,
KeyValueName = $"{keyName}${label}",
ResourceGroupName = <resource_group_name>,
Value = keyValue.Apply(value => $"{{\"uri\":\"{value}\"}}")
}
Where keyValue is a SecretUri from a KeyVault Secret.
What happened?
See https://www.pulumi.com/registry/packages/azure-native/api-docs/appconfiguration/keyvalue/#create and compare with https://www.pulumi.com/registry/packages/azure/api-docs/appconfiguration/configurationkey/#create
in the latter it allows you to create a VaultKeyReference. In the former it does not.
On https://github.com/pulumi/pulumi-azure it claims 'Azure Native provides complete coverage of Azure resources' and 'Azure Classic. .. has fewer resources and resource options' But this does not appear to be true
Steps to reproduce
Can't reproduce an API omission!
Expected Behavior
AzureNative to permit you to create an Azure App Configuration KeyVault reference
Actual Behavior
n/a
Versions used
Pulumi 3.29.1
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).