Class UpdateSnoozeRequest (2.21.0)

Version latest

• 2.21.0 (latest)
• 2.20.0
• 2.19.4
• 2.18.0
• 2.17.0
• 2.16.0
• 2.15.1
• 2.14.2
• 2.13.0
• 2.12.0
• 2.11.3
• 2.10.1
• 2.9.2
• 2.8.0
• 2.7.0
• 2.6.0
• 2.5.2
• 2.4.2
• 2.3.0
• 2.2.1
• 2.1.0
• 2.0.1
• 1.1.2
• 1.0.0
• 0.36.2
• 0.35.0
• 0.34.0
• 0.33.0
• 0.32.0

UpdateSnoozeRequest(mapping=None, *, ignore_unknown_fields=False, **kwargs)

The message definition for updating a Snooze. The field, snooze.name identifies the Snooze to be updated. The remainder of snooze gives the content the Snooze in question will be assigned.

What fields can be updated depends on the start time and end time of the Snooze.

• end time is in the past: These Snooze\ s are considered read-only and cannot be updated.
• start time is in the past and end time is in the future: display_name and interval.end_time can be updated.
• start time is in the future: display_name, interval.start_time and interval.end_time can be updated.

Attributes
Name	Description
snooze	google.cloud.monitoring_v3.types.Snooze Required. The Snooze to update. Must have the name field present.
update_mask	google.protobuf.field_mask_pb2.FieldMask Required. The fields to update. For each field listed in update_mask: - If the Snooze object supplied in the UpdateSnoozeRequest has a value for that field, the value of the field in the existing Snooze will be set to the value of the field in the supplied Snooze. - If the field does not have a value in the supplied Snooze, the field in the existing Snooze is set to its default value. Fields not listed retain their existing value. The following are the field names that are accepted in update_mask: - display_name - interval.start_time - interval.end_time That said, the start time and end time of the Snooze determines which fields can legally be updated. Before attempting an update, users should consult the documentation for UpdateSnoozeRequest, which talks about which fields can be updated.