Skip to main content

Resources and Data Sources

This page lists the Terraform provider types that are currently implemented in code.

Resources​

The provider currently registers these resources:

  • statuspage_hierarchy_level
  • statuspage_hierarchy_item
  • statuspage_status_definition
  • statuspage_lifecycle_stage
  • statuspage_maintenance_lifecycle_stage
  • statuspage_site_settings
  • statuspage_role_definition
  • statuspage_role_binding
  • statuspage_sso_group_mapping
  • statuspage_preset_message
  • statuspage_slack_app_settings
  • statuspage_slack_channel_reminder_settings
  • statuspage_custom_view

Data sources​

The provider currently registers these data sources:

  • statuspage_hierarchy_levels
  • statuspage_hierarchy_item
  • statuspage_custom_views
  • statuspage_rss_feeds
  • statuspage_status_events

Important behavior notes​

Hierarchy items​

Hierarchy item status is computed and read-only in Terraform. The resource schema explicitly documents that status changes must happen through incidents or maintenance.

Site settings​

statuspage_site_settings is a singleton resource. Removing it from Terraform state does not delete settings from the API.

RBAC resources​

statuspage_role_definition and statuspage_role_binding support organization and page scope. Organization-scoped resources only require organization_id; page-scoped resources require both organization_id and status_page_id.

Built-in roles are available everywhere. Custom RBAC definitions and non-built-in role bindings require advanced RBAC and become read-only if the workspace drops below that plan.

Slack app settings​

statuspage_slack_app_settings is also modeled as a singleton resource. Sensitive values such as client secret and signing secret are treated as write-only inputs.

Custom views​

Custom views are managed by name, description, and component IDs. The provider imports them by short_code.

RSS​

RSS feeds are currently available as a data source, not a managed resource.