uptimeify_im_org_settings
Incident Management settings of the token's organization (one per organization). Creating it adopts the existing settings and applies the configured values; destroying it only removes it from the state, the settings stay. Import with any id, e.g. org.
Incident Management settings of the token's organization (one per organization). Creating it adopts the existing settings and applies the configured values; destroying it only removes it from the state, the settings stay. Import with any id, e.g. org.
Example Usage
# One per organization; destroy only removes it from the state.
resource "uptimeify_im_org_settings" "this" {
monitoring_bridge = "both"
overage_enabled = false
fallback_channel_id = 3
}Schema
Optional
fallback_channel_id(Number) Active Incident Management channel paged when an escalation runs out. Unset clears it.monitoring_bridge(String) Where classic monitoring alerts go:im_only,classic_onlyorboth. Unset = keep the current value.overage_enabled(Boolean) Allow Incident Management usage beyond the plan (billed as overage). Unset = keep the current value.
Read-Only
enabled(Boolean) Whether Incident Management is active (POST /api/im/activate; read only here).id(String) The organization id.organization_id(Number)
Import
Import is supported using the following syntax:
The terraform import command can be used, for example:
# Any id works: the settings belong to the token's organization.
terraform import uptimeify_im_org_settings.this orguptimeify_im_escalation_tier
An escalation tier of an Incident Management team. Creating a tier also creates its default schedule (default_schedule_id, rotation mode none) whose single rotation is member_user_ids; further schedules of the tier are uptimeify_im_schedule. Import with <team_id>/<tier_id>.
uptimeify_im_outbound_integration
An Incident Management outbound integration: forwards incident events to Slack, Microsoft Teams, Discord, Jira, PagerDuty (Events v2), Opsgenie or a generic webhook. Incident Management must be active for the organization. URLs, tokens, keys and header values are secrets the API never returns, so they are write-only here; has_* tells whether one is stored. Import with the numeric id.