Data Sources
uptimeify_im_schedule
Look up one on-call schedule by id or by name (exactly one). The default schedules of different teams can share a name (Tier 1 schedule), so team_id narrows a lookup by name. Fails when no or several schedules match.
Look up one on-call schedule by id or by name (exactly one). The default schedules of different teams can share a name (Tier 1 schedule), so team_id narrows a lookup by name. Fails when no or several schedules match.
Example Usage
data "uptimeify_im_team" "platform" {
name = "Platform"
}
# Default schedules of different teams can share a name, team_id narrows the lookup.
data "uptimeify_im_schedule" "first_tier" {
name = "Tier 1 schedule"
team_id = tonumber(data.uptimeify_im_team.platform.id)
}
# Take the first member of the looked-up schedule off call for the holidays.
resource "uptimeify_im_schedule_override" "holiday" {
schedule_id = data.uptimeify_im_schedule.first_tier.id
user_id = data.uptimeify_im_schedule.first_tier.rotations[0].members[0]
type = "offline"
starts_at = "2030-08-01T00:00:00Z"
ends_at = "2030-08-15T00:00:00Z"
}Schema
Optional
id(String) Numeric schedule id.name(String)team_id(Number) Team of the schedule; narrows a lookup byname, conflicts withid.
Read-Only
auto_rotation_size(Number)created_at(String)custom_repeat_unit(String)custom_repeat_value(Number)effective_from(String)effective_until(String)organization_id(Number)rotation_mode(String)rotation_repeats(String)rotations(Attributes List) Ordered rotation groups. (see below for nested schema)round_robin_size(Number)starts_on_date_of_month(Number)starts_on_day_of_week(Number)starts_on_time(String)team_name(String)tier_id(Number)timezone(String)updated_at(String)weekly_schedules(Attributes List) Weekly windows; empty = around the clock. (see below for nested schema)
Nested Schema for rotations
Read-Only:
members(List of String) User ids in order.
Nested Schema for weekly_schedules
Read-Only:
days(List of Number) ISO weekdays, 1 = Monday to 7 = Sunday.from(String)until(String)