Open pawel-ochman opened 12 months ago
Thank you for opening this issue, we will look into it.
Additional investigation needed
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AnatoliB, @Francisco-Gamino, @shreyabatra4.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AnatoliB, @Francisco-Gamino, @shreyabatra4.
Describe the bug
We are currently developing a simple Azure Function App that utilizes a Cosmos DB Change Feed Trigger. This trigger includes an option to set a StartFromTime for the cursor, which is intended to prevent the processing of all data within the container from the beginning. The recommended format for the StartTime is ISO 8601.
The issue arises when configuring the service using Azure CLI. Despite entering the StartFromTime in the correct ISO 8601 format, the configuration value format appears to be altered upon execution of the CLI command. This unexpected change in the timestamp format leads to an issue where the Function App is unable to correctly map the trigger endpoint.
Related command
az functionapp config appsettings set --name $name --resource-group $group --settings "test_StartFromTime=2023-01-03T12:12:23Z"
Errors
Issue script & Debug output
the problem is not with the script, only with the result
Expected behavior
Az Cli should set the value in the defined format
Environment Summary
azure-cli 2.53.1
core 2.53.1 telemetry 1.1.0
Dependencies: msal 1.24.0b2 azure-mgmt-resource 23.1.0b2
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe' Extensions directory 'C:\Users\pawel.azure\cliextensions'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb 7 2023, 17:05:00) [MSC v.1929 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
No response