You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ You can leverage this library in your automation framework to process circuit ma
24
24
-**provider**: identifies the provider of the service that is the subject of the maintenance notification.
25
25
-**account**: identifies an account associated with the service that is the subject of the maintenance notification.
26
26
-**maintenance_id**: contains text that uniquely identifies (at least within the context of a specific provider) the maintenance that is the subject of the notification.
27
-
-**circuits**: list of circuits affected by the maintenance notification and their specific impact. Note that in a maintenance canceled notification, some providers omit the circuit list, so this may be blank for maintenance notifications with a status of CANCELLED.
27
+
-**circuits**: list of circuits affected by the maintenance notification and their specific impact. Note that in a maintenance canceled or completed notification, some providers omit the circuit list, so this may be blank for maintenance notifications with a status of CANCELLED or COMPLETED.
28
28
-**start**: timestamp that defines the starting date/time of the maintenance in GMT.
29
29
-**end**: timestamp that defines the ending date/time of the maintenance in GMT.
30
30
-**stamp**: timestamp that defines the update date/time of the maintenance in GMT.
@@ -71,12 +71,15 @@ By default, there is a `GenericProvider` that supports a `SimpleProcessor` using
0 commit comments