AlertProcessingRule 2021-08-08 property EffectiveFrom pattern is not consistent with the service actually supported

[Tao]

The API specs is below:

azure-rest-api-specs/specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2021-08-08/AlertProcessingRules.json

Lines 539 to 543 in 3c18ef0

 "effectiveFrom": { 
   "type": "string", 
   "pattern": "^(?:(\\d{4}-\\d{2}-\\d{2})T(\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?))$", 
   "description": "Scheduling effective from time. Date-Time in ISO-8601 format without timezone suffix." 
 }, 

But using the below value in the request, which can match the given RegEx pattern:

effectiveFrom = "2022-01-01T01:02:03.0123"

Server response:

{
   "error": {
     "code": "BadRequest",
     "message": "Invalid input parameters: Wrong DateTime format of the parameter: 'effectiveFrom', with value: '2022-01-01T01:02:03.0123'. Expected date time format is 'yyyy'-'MM'-'dd'T'HH':'mm':'ss'."
   }
}

Test with empty string effectiveFrom = "", the same error returns
Maybe the correct pattern for effectiveFrom and effectiveUntil should be "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}$"

---

azure-rest-api-specs/specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2021-08-08/AlertProcessingRules.json

Lines 583 to 586 in 3c18ef0

 "startTime": { 
   "type": "string", 
   "description": "Start time for recurrence." 
 }, 

Besides, startTime and endTime in above specs should have a pattern "^\\d{2}:\\d{2}:\\d{2}$" according to server response.

"Invalid input parameters: Wrong Time format of the parameter: 'startTime', with value: ''. Expected date time format is: 'HH':'mm':'ss'."

[Deleted user]

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

Issue Details

---

The API specs is below:

azure-rest-api-specs/specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2021-08-08/AlertProcessingRules.json

Lines 539 to 543 in 3c18ef0

 "effectiveFrom": { 
   "type": "string", 
   "pattern": "^(?:(\\d{4}-\\d{2}-\\d{2})T(\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?))$", 
   "description": "Scheduling effective from time. Date-Time in ISO-8601 format without timezone suffix." 
 }, 

But using the below value in the request, which can match the given RegEx pattern:

effectiveFrom = "2022-01-01T01:02:03.0123"

Server response:

{
   "error": {
     "code": "BadRequest",
     "message": "Invalid input parameters: Wrong DateTime format of the parameter: 'effectiveFrom', with value: '2022-01-01T01:02:03.0123'. Expected date time format is 'yyyy'-'MM'-'dd'T'HH':'mm':'ss'."
   }
}

Maybe the correct pattern should be "^(?:(\\d{4}-\\d{2}-\\d{2})T(\\d{2}:\\d{2}:\\d{2}))$"

Author:	teowa
Assignees:	-
Labels:	Service Attention, needs-triage, Alerts Management
Milestone:	-