Uptimeify Docs
Ressourcen

uptimeify_im_schedule_override

Ressource uptimeify_im_schedule_override: Beispiel, alle Attribute, Import.

Die Beschreibungen auf dieser Seite kommen direkt aus dem Provider-Schema und sind deshalb englisch.

An override (vacation, swap) on an on-call schedule. Import with <schedule_id>/<override_id>.

Beispiel

# Alice is on vacation, Bob covers.
resource "uptimeify_im_schedule_override" "vacation" {
  schedule_id         = uptimeify_im_schedule.weekly.id
  user_id             = uptimeify_im_team_member.alice.user_id
  type                = "offline"
  covered_by_user_ids = [uptimeify_im_team_member.bob.user_id]
  starts_at           = "2030-08-01T00:00:00Z"
  ends_at             = "2030-08-15T00:00:00Z"
}

Schema

Pflichtfelder

  • 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.
  • schedule_id (Number)
  • starts_at (String) Start. RFC3339 timestamp. The API answers in UTC with milliseconds, another spelling of the same instant is kept as written.
  • 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.

Nur lesbar

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

Import

Import geht so:

Mit tofu import bzw. terraform import, zum Beispiel:

# <schedule_id>/<override_id>
terraform import uptimeify_im_schedule_override.vacation 78/90

Auf dieser Seite