Azure App Configuration resource manager api is decoding characters in key and label before reaching the url end point.

Athi Narayanan Jeyaraj 0 Microsoft Employee

App Config resource manager API to create or update Key Values is giving 404 error when the key has a forward slash in it.

Athi Narayanan Jeyaraj 0 Reputation points Microsoft Employee

2024-10-22T05:29:52.7933333+00:00
https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/keyValues/Test%2F123?api-version=2024-05-01

This gives 404, since the Test%2F123 gets decoded to Test/123 before reaching its controller and path /KeyValues/Test/123 is not found.

This completely block feature flag operations because feature flag key requires a forward slash in it, .appconfig.featureflag/{FFKey}
Athi Narayanan Jeyaraj 0 Reputation points Microsoft Employee

2024-10-22T05:31:07.9233333+00:00

https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppConfiguration/configurationStores/{configStoreName}/keyValues/Test%2F123?api-version=2024-05-01

This gives 404, since the Test%2F123 gets decoded to Test/123 before reaching its controller and path /KeyValues/Test/123 is not found.

This completely block feature flag operations because feature flag key requires a forward slash in it, .appconfig.featureflag/{FFKey}

1 answer

LeelaRajeshSayana-MSFT 16,786 Reputation points

2024-10-22T22:11:06.9033333+00:00
Hi @Athi Narayanan Jeyaraj The API call you are trying to use is meant for use in ARM template deployments alone. If you are trying hit the API with a PUT call, it will likely fail.

There is another API in the data plane which lets you create a Key-Value under feature flag. Try the following API end point

PUT {endpoint}/kv/{key}?api-version=2023-11-01

For the key, you can pass a value similar to this .appconfig.featureflag%2Ftest Refer the documentation of the API endpoint Put Key Value for additional details.

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.
Please sign in to rate this answer.
Athi Narayanan Jeyaraj 0 Reputation points Microsoft Employee

2024-10-22T22:42:04.9833333+00:00

Hi @LeelaRajeshSayana-MSFT
Thanks for your response.
We have been using Azure.Resourcemanager APIs through the SDK for managing our azure resources. Put call to that URL has been working fine for key-values, we are encountering the issue only when there is a forward slash in the key or label.

Since the API is exposed outside Resource Manager Key Values - Create Or Update and also the SDK AppConfigurationKeyValueCollection.CreateOrUpdateAsync is available for external use, it would be great if this gets fixed.

As for this fix, if you are using azure app service to host the api this might be the fix Azure decoding URL

LeelaRajeshSayana-MSFT 16,786 Reputation points

2024-10-28T12:49:02.7833333+00:00

HI @Athi Narayanan Jeyaraj Thank you for your insights and feedback on this. We will take this to the product team.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure App Configuration resource manager api is decoding characters in key and label before reaching the url end point.

1 answer

Your answer