GoSpace Manager

Version v0.11.0

Manage Google Workspace resources using a developer-friendly CLI written in Go

patch

Updates an event. This method supports patch semantics.

Synopsis

Implements the API documented at https://developers.google.com/calendar/api/v3/reference/events/patch

gsm events patch [flags]

Options

      --addConferenceData                 Whether to add a Meet conference to the event.
      --anyoneCanAddSelf                  Whether anyone can invite themselves to the event (currently works for Google+ events only).
      --attendees strings                 Must be given in the following format: "--attendees "email=some.address@domain.com;resource=[true|false];optional=[true|false];responseStatus=accepted""
                                          Can be used multiple times to invite more than one attendee.
                                          If you batchPatch an event, rememder to specify ALL attendees (not just new ones)!
      --attendeesOmitted                  Whether attendees may have been omitted from the event's representation.
                                          When retrieving an event, this may be due to a restriction specified by the maxAttendee query parameter.
                                          When updating an event, this can be used to only update the participant's response.
      --calendarId string                 Calendar identifier. To retrieve calendar IDs call the calendarList.list method.
                                          If you want to access the primary calendar of the currently logged in user, use the "primary" keyword. (default "primary")
      --colorId string                    The color of the event.
                                          This is an ID referring to an entry in the event section of the colors definition (see the colors endpoint).
      --conferenceDataVersion int         Version number of conference data supported by the API client.
                                          Version 0 assumes no conference data support and ignores conference data in the event's body.
                                          Version 1 enables support for copying of ConferenceData as well as for creating new conferences using the createRequest field of conferenceData. (default 1)
      --description string                Description of the event. Can contain HTML.
      --endDate string                    The date, in the format "yyyy-mm-dd", if this is an all-day event.
      --endDateTime string                The time, as a combined date-time value (formatted according to RFC3339).
                                          A time zone offset is required unless a time zone is explicitly specified in timeZone.
      --endTimeZone string                The time zone in which the time is specified.
                                          (Formatted as an IANA Time Zone Database name, e.g. "Europe/Zurich".)
                                          For recurring events this field is required and specifies the time zone in which the recurrence is expanded.
                                          For single events this field is optional and indicates a custom time zone for the event start/end.
      --eventId string                    Event identifier.
      --fields string                     Fields allows partial responses to be retrieved.
                                          See https://developers.google.com/gdata/docs/2.0/basics#PartialResponse for more information.
      --fileUrl strings                   URL link to the attachment.
                                          For adding Google Drive file attachments use the same format as in alternateLink property of the Files resource in the Drive API.
                                          Can be used multiple times to add more than one file.
      --guestsCanInviteOthers             Whether attendees other than the organizer can invite others to the event.
      --guestsCanModify                   Whether attendees other than the organizer can modify the event.
      --guestsCanSeeOtherGuests           Whether attendees other than the organizer can see who the event's attendees are.
  -h, --help                              help for patch
      --id string                         Opaque identifier of the event. When creating new single or recurring events, you can specify their IDs.
                                          Provided IDs must follow these rules:
                                          characters allowed in the ID are those used in base32hex encoding, i.e. lowercase letters a-v and digits 0-9, see section 3.1.2 in RFC2938
                                          the length of the ID must be between 5 and 1024 characters
                                          the ID must be unique per calendar
                                          Due to the globally distributed nature of the system, we cannot guarantee that ID collisions will be detected at event creation time.
                                          To minimize the risk of collisions we recommend using an established UUID algorithm such as one described in RFC4122.
                                          If you do not specify an ID, it will be automatically generated by the server.
                                          
                                          Note that the icalUID and the id are not identical and only one of them should be supplied at event creation time.
                                          One difference in their semantics is that in recurring events, all occurrences of one event have different ids while they all share the same icalUIDs.
      --location string                   Geographic location of the event as free-form text.
      --maxAttendees int                  The maximum number of attendees to include in the response.
                                          If there are more than the specified number of attendees, only the participant is returned.
      --privateExtendedProperty strings   Properties that are private to the copy of the event that appears on this calendar.
      --recurrence strings                List of RRULE, EXRULE, RDATE and EXDATE lines for a recurring event, as specified in RFC5545.
                                          Note that DTSTART and DTEND lines are not allowed in this field; event start and end times are specified in the start and end fields.
                                          This field is omitted for single events or instances of recurring events.
      --reminderOverride strings          If the event doesn't use the default reminders, this lists the reminders specific to the event, or, if not set, indicates that no reminders are set for this event.
                                          The maximum number of override reminders is 5.
                                          Must be specified in the following format: "--reminderOverride "method=[email|popup];minutes=[0-40320]""
                                          Can be used multiple times to specify more than one reminder override.
      --sendUpdates string                Guests who should receive notifications about the event update (for example, title changes, etc.).
                                          [all|externalOnly|none]
                                          all           - Notifications are sent to all guests.
                                          externalOnly  - Notifications are sent to non-Google Calendar guests only.
                                          none          - No notifications are sent. This value should only be used for migration use cases (note that in most migration cases the import method should be used). (default "none")
      --sequence int                      Sequence number as per iCalendar.
      --sharedExtendedProperty strings    Properties that are shared between copies of the event on other attendees' calendars.
      --startDate string                  The date, in the format "yyyy-mm-dd", if this is an all-day event.
      --startDateTime string              The time, as a combined date-time value (formatted according to RFC3339).
                                          A time zone offset is required unless a time zone is explicitly specified in timeZone.
      --startTimeZone string              The time zone in which the time is specified.
                                          (Formatted as an IANA Time Zone Database name, e.g. "Europe/Zurich".)
                                          For recurring events this field is required and specifies the time zone in which the recurrence is expanded.
                                          For single events this field is optional and indicates a custom time zone for the event start/end.
      --status string                     Status of the event.
                                          [confirmed|tentative|cancelled]
                                          confirmed  - The event is confirmed. This is the default status.
                                          tentative  - The event is tentatively confirmed.
                                          cancelled  - The event is cancelled (deleted). The list method returns cancelled events only on incremental sync (when syncToken or updatedMin are specified) or if the showDeleted flag is set to true. The get method always returns them.
                                          A cancelled status represents two different states depending on the event type:
                                          
                                          Cancelled exceptions of an uncancelled recurring event indicate that this instance should no longer be presented to the user. Clients should store these events for the lifetime of the parent recurring event.
                                          Cancelled exceptions are only guaranteed to have values for the id, recurringEventId and originalStartTime fields populated. The other fields might be empty.
                                          
                                          All other cancelled events represent deleted events. Clients should remove their locally synced copies. Such cancelled events will eventually disappear, so do not rely on them being available indefinitely.
                                          Deleted events are only guaranteed to have the id field populated.
                                          
                                          On the organizer's calendar, cancelled events continue to expose event details (summary, location, etc.) so that they can be restored (undeleted). Similarly, the events to which the user was invited and that they manually removed continue to provide details. However, incremental sync requests with showDeleted set to false will not return these details.
                                          If an event changes its organizer (for example via the move operation) and the original organizer is not on the attendee list, it will leave behind a cancelled event where only the id field is guaranteed to be populated.
      --summary string                    Title of the event.
      --supportsAttachments               Whether API client performing operation supports event attachments.
      --transparency string               Whether the event blocks time on the calendar.
                                          [opaque|transparent]
                                          opaque       - Default value. The event does block time on the calendar. This is equivalent to setting Show me as to Busy in the Calendar UI.
                                          transparent  - The event does not block time on the calendar. This is equivalent to setting Show me as to Available in the Calendar UI.
      --useDefaultReminders               Whether the default reminders of the calendar apply to the event.
      --visibility string                 Visibility of the event.
                                          [default|public|private|confidential]
                                          default       - Uses the default visibility for events on the calendar. This is the default value.
                                          public        - The event is public and event details are visible to all readers of the calendar.
                                          private       - The event is private and only event attendees may view event details.
                                          confidential  - The event is private. This value is provided for compatibility reasons.

Options inherited from parent commands

      --compressOutput         By default, GSM outputs "pretty" (indented) objects. By setting this flag, GSM's output will be compressed. This may or may not improve performance in scripts.
      --config string          config file (default is $HOME/.config/gsm/.gsm.yaml)
      --delay int              This delay (plus a random jitter between 0 and 50) will be applied after every command to avoid reaching quota and rate limits. Set to 0 to disable.
      --dwdSubject string      Specify a subject used for DWD impersonation (overrides value in config file)
      --log string             Set the path of the log file. Default is either ~/gsm.log or defined in your config file
      --maxElapsedTime int     This is the maximum total time that will be spent retrying a request in minutes. (default 15)
      --maxRetryInterval int   This is the maximum interval that will be used between retry attempts in seconds. (default 320)
      --redirectPort int       This is the TCP port on which GSM will create web server if you authenticate with a user account for the first time. This is necessary for the OAuth flow. See https://developers.google.com/identity/protocols/oauth2/native-app#redirect-uri_loopback (default 8081)
      --retryOn ints           Specify the HTTP error code(s) that GSM should retry on. Note that GSM will always retry on HTTP 403 errors that indicate a quota / rate limit error
      --streamOutput           Setting this flag will cause GSM to output slice values to stdout one by one, instead of one large object

SEE ALSO