Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]The description values of AdvancedScheduleMonthlyOccurrence are inconsistent with Azure Portal #28901

Open
sinbai opened this issue Apr 30, 2024 · 0 comments
Labels
Automation bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue points to a problem in the management-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@sinbai
Copy link

sinbai commented Apr 30, 2024

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/20d333fa60a4a81acfd01a7bd56dd9c552301afe/specification/automation/resource-manager/Microsoft.Automation/stable/2019-06-01/softwareUpdateConfiguration.json#L644C6-L644C39

API Spec version

2019-06-01

Describe the bug

It was found that the possible values of AdvancedScheduleMonthlyOccurrence should be 1, 2,3,4,-1 ,corresponds to "First", "Second", "Third", "Fourth" and "Last" in the Azure Portal respectively. Details are as follows.
image

However, the description of AdvancedScheduleMonthlyOccurrence in swagger is "Occurrence of the week within the month. Must be between 1 and 5".

Expected behavior

The possible values of AdvancedScheduleMonthlyOccurrence should be 1, 2,3,4,-1.

Actual behavior

The description values of AdvancedScheduleMonthlyOccurrence between 1 and 5.

Reproduction Steps

Create corresponding resources in the portal and view the values.

Environment

No response

@sinbai sinbai added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 30, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Apr 30, 2024
@zzhxiaofeng zzhxiaofeng added the Mgmt This issue points to a problem in the management-plane of the library. label May 8, 2024
@akning-ms akning-ms added Automation Service Attention This issue is responsible by Azure service team. labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Automation bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue points to a problem in the management-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants