Uptimeify Docs
Resources

uptimeify_im_team_override

An override (vacation, swap) owned by an Incident Management team, optionally on one of its schedules. Import with <team_id>/<override_id>.

An override (vacation, swap) owned by an Incident Management team, optionally on one of its schedules. Import with <team_id>/<override_id>.

Example Usage

# Bob takes over for a release night, for the whole team.
resource "uptimeify_im_team_override" "release" {
  team_id   = uptimeify_im_team.platform.id
  user_id   = uptimeify_im_team_member.bob.user_id
  type      = "online"
  starts_at = "2030-09-01T18:00:00+02:00"
  ends_at   = "2030-09-02T06:00:00+02:00"
}

Schema

Required

  • ends_at (String) End, after starts_at. RFC3339 timestamp. The API answers in UTC with milliseconds, another spelling of the same instant is kept as written.
  • starts_at (String) Start. RFC3339 timestamp. The API answers in UTC with milliseconds, another spelling of the same instant is kept as written.
  • team_id (Number)
  • type (String) online (user takes the shift) or offline (user is away).
  • user_id (String) User going online or offline; an admin, editor or responder of the organization.

Optional

  • apply_scope (String) this_team (default) or all_teams.
  • covered_by_user_ids (Set of String) offline only: who covers (at most 200). Empty = a gap that auto fill-up backstops.
  • escalation_tier_order (Number) Only this tier position; unset = all tiers.
  • schedule_id (Number) A schedule of this team; unset = team-level override.

Read-Only

  • created_at (String)
  • id (String) <team_id>/<override_id>.
  • override_id (Number) Numeric override id.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# <team_id>/<override_id>
terraform import uptimeify_im_team_override.release 12/91

On this page