Documented parameters allowed values #10565
-
I've found while authoring templates, that documentation on parameters sometimes shows an example value, but not the enumeration of the other possible ones, or a link to its definition. For example, the documentation for timeZoneId in the resource "Microsoft.DevTestLab/schedules" shows one possible value, but if I want to specify a different one, I don't know where to find it. Neither going to the portal and listing the possible values listed to select would help, as they are persisted with another name if I look them after created in the resource explorer. If I choose "(UTC-03:00) City of Buenos Aires", on resource explorer I find the property set as "Argentina Standard Time". So, bringing this information in the documentation will be very useful. For this I ended up in a stack overflow response of someone who listed the time zones from the windows registry, and it worked, but it was a lucky shoot, and I would like to be sure of the values I'm setting, and also where they come from. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
At the moment, those docs are auto generated based on what is in the API specification.
We have the specifications also published here: E.g. "timeZoneId": {
"description": "The time zone ID (e.g. Pacific Standard time).",
"type": "string"
} These are owned and controlled by the Owner of the Resource Provider e.g. Compare this description to the description on the Microsoft.Compute/VirtualMachineScaleset "timeZone": {
"type": "string",
"description": "Specifies the time zone of the virtual machine. e.g. \"Pacific Standard Time\". <br><br> Possible values can be [TimeZoneInfo.Id](https://docs.microsoft.com/dotnet/api/system.timezoneinfo.id?#System_TimeZoneInfo_Id) value from time zones returned by [TimeZoneInfo.GetSystemTimeZones](https://docs.microsoft.com/dotnet/api/system.timezoneinfo.getsystemtimezones)."
}, which ends up as following in the docs page
I think the best action might be, if you could open the issue directly on the DevTestLab documentation page?
|
Beta Was this translation helpful? Give feedback.
Thank you for your detailed analysis and guidance. I've submitted the issue to the DevTestLabs documentation page here.