AppConfig Key Vault reference import causes invalid Content Type for YAML files

[shanmukhsumanth]

Describe the bug

While we are trying to deploy Key Vault values in yaml files, its not supporting yaml formart. "Support settings with JSON content type" for AppConfig and I suspect this is what is impacting me.

Related command

az appconfig kv import

Errors

Failed to import 'yaml' file format with 'application/vnd.microsoft.appconfig.keyvaultref+json;charset=utf-8' content type. Please provide JSON file format to match your content type.

Issue script & Debug output

Same error with Debug command as well

cli.azure.cli.core.azclierror: Failed to import 'yaml' file format with 'application/vnd.microsoft.appconfig.keyvaultref+json;charset=utf-8' content type. Please provide JSON file format to match your content type.
az_command_data_logger:Failed to import 'yaml' file format with 'application/vnd.microsoft.appconfig.keyvaultref+json;charset=utf-8' content type. Please provide JSON file format to match your content type.

Expected behavior

AppConfig Key Vault data deployment should be successfully to Azure dashboard with yaml format.

Environment Summary

{
"azure-cli": "2.65.0",
"azure-cli-core": "2.65.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"ssh": "1.1.3"
}

Additional context

No response

[azure-client-tools-bot-prd]

Hi @shanmukhsumanth,

2.65.0 is not the latest Azure CLI(2.69.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• AppConfig Key Vault reference import causes invalid Content Type for YAML files #14845

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

From @avanigupta's comment, the issue occurred because importing key-values from a YAML file with JSON content-type is not supported. If you still want this feature, you can open a new issue in the https://github.com/Azure/AppConfiguration/issues repo to get it prioritized.

Reference:

• AppConfig Key Vault reference import causes invalid Content Type for YAML files #14845 (comment)

Solution 2:

From @ChristopherL-STCU's comment, YAML import was deprecated, and there are no plans to support YAML functionality. If YAML deprecation was a mistake and this functionality is intended, then this issue can remain open to track it.

Reference:

• AppConfig Key Vault reference import causes invalid Content Type for YAML files #14845 (comment)

Powered by issue-sentinel

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shenmuxiaosen, @avanigupta.

[albertofori]

Hello @shanmukhsumanth,

This behavior is intended, as we require a file in JSON format to import key-values correctly. I recommend converting your files to JSON format to ensure proper import with the JSON content type.

Also, to maintain the content type of your configuration values without specifying any content type during import, you can export the configuration using the KVSet content profile. Although this still necessitates a JSON file, it preserves all key-value properties.

I hope this helps.

[shanmukhsumanth]

Hi @albertofori ,

Thanks for the response, I wanted to understand if you have any plan to support YAML file deployment in the future because the document provided by Microsoft, states that file formats supported for this config deployment are JSON, yml, properties, etc,

Reference doc: https://learn.microsoft.com/en-us/cli/azure/appconfig/kv?view=azure-cli-latest#az-appconfig-kv-import

[albertofori]

Hi @shanmukhsumanth ,

To ensure clarity and uniformity, we currently do no have plans to support this as we consider the json content type to be unique to the json formatted document. If a key-value has a json content type, we expect the value to be formatted as such. In this case, this warrants a key-value in json format, with a valid json value.