Uptimeify Docs
Datenquellen

uptimeify_im_outbound_integration

Datenquelle uptimeify_im_outbound_integration: Beispiel, alle Attribute.

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

Look up one Incident Management outbound integration by id or by name (exactly one). Fails when no or several integrations match the name. Secrets are never returned.

Beispiel

data "uptimeify_im_outbound_integration" "jira" {
  name = "Jira OPS"
}

output "jira_project" {
  value = data.uptimeify_im_outbound_integration.jira.project_key
}

Schema

Optional

  • id (String) Numeric integration id.
  • name (String)

Nur lesbar

  • base_url (String) jira: site URL, https only, required.
  • created_at (String)
  • email (String) jira: account email, required.
  • event_kinds (List of String) Events to forward: incident_created, acknowledged, severity_changed, status_changed, comment, resolved. Unset = all, except jira, where the server stores ["incident_created"]. Removing it from the configuration keeps the stored list.
  • filter_severities (List of String) Only these severities, sev1 to sev4. Unset = all.
  • filter_team_ids (List of Number) Only incidents of these teams (of the organization). Unset = all.
  • has_api_key (Boolean) Whether an Opsgenie API key is stored.
  • has_api_token (Boolean) Whether a Jira API token is stored.
  • has_bearer_token (Boolean) Whether a bearer token is stored.
  • has_headers (Boolean) Whether custom headers are stored.
  • has_routing_key (Boolean) Whether a PagerDuty routing key is stored.
  • has_webhook_url (Boolean) Whether a webhook URL is stored.
  • is_active (Boolean) Default true.
  • organization_id (Number)
  • project_key (String) jira: project key, required.
  • team_id (Number) Owning team; unset = organization-wide (needs an org admin).
  • type (String) slack, teams, discord, jira, pagerduty_v2, opsgenie or webhook. Changing it replaces the integration.
  • updated_at (String)

Auf dieser Seite