Terraform Provider Version 3.1.0: Granular Security and Configuration
All Quiet Terraform Provider v3.1.0 adds inbound webhook security, dynamic Slack channels, status page privacy controls, routing uptime exclusions, and incident engagement report settings.
Published: Tuesday, 11 August 2026
All Quiet Terraform Provider v3.1.0 is now available. This release brings recent UI capabilities into Terraform: granular inbound webhook security, dynamic Slack channels, status page privacy controls, routing uptime exclusions, and incident engagement report settings for users and teams.
Version 3.1.0 is the Terraform follow-up to several product updates shipped in the All Quiet web app. If you configure these features in the UI today, you can now manage the same settings as code.
Related product updates
These changelog entries describe the underlying UI features now available in Terraform:
- Inbound Webhook Authentication and Security — IP filtering and bearer token authentication for webhook integrations
- Dynamic Incident Channels for Slack, MS Teams, and Mattermost — dedicated incident channels per event
- Improved Slack, Teams and Mattermost Message Formats — hide activity history in Slack incident messages
- Additional New Privacy Controls for Status Pages — control what visitors see on public status pages
- Status Pages public incident history — incident history pages and visibility settings
- Affects Uptime Toggle and Routing Rule Comments — exclude incidents from uptime calculations in routing rules
Outbound Integrations
We updated the allquiet_outbound_integration resource to improve reliability and reduce configuration errors.
Slack and Mattermost Severity Settings
When you enable severity_based_channel_settings for Slack or Mattermost, you must now explicitly set an entry for all severity levels. This requirement prevents accidental omissions. If you only want to send critical incidents to a channel, you must assign empty lists to the minor and warning severities.
severity_based_channel_settings = {
selected_channel_ids_minor = []
selected_channel_ids_warning = []
selected_channel_ids_critical = ["<channel-id>"]
}
Slack Specific Enhancements
You now have more control over how Slack handles incidents:
- Dynamic Channels: Use
slack_settings.dedicated_channelto automatically create a dedicated Slack channel per incident. - Activity History: Set
hide_activity_history = trueto hide incident history in the interactive incident messages sent to your Slack channels. The default value isfalse.
Inbound Integrations and Security
Security and privacy dictate how you handle inbound alerts. The allquiet_integration resource now supports strict authentication rules. You can verify these settings directly in the All Quiet UI under Integrations > [webhook integration] > Authentication/Security.
You can apply the following security models:
- IP Filtering: Set
webhook_authentication.private_ip_filterto a valid CIDR block. The system will accept payloads from matching IPs and reject non-matching traffic. - Bearer Token: Set
webhook_authentication.type = "bearer"and provide a token. The system will reject any POST request missing the correct token in the header. - Combined Security: Apply both an IP filter and a bearer token to ensure maximum security for your incoming webhooks.
Status Page Configurations
Version 3.1.0 brings existing status page settings from the UI directly into the allquiet_status_page resource.
You can also customize the presentation of service groups. If you omit public_display_name in a service group that contains only a single service, the status page will display that service individually rather than grouping it.
| Setting | Default | Description |
|---|---|---|
public_display_live_state_only |
false |
Shows only the current service status. Removes the uptime percentage and historical bar graphs. |
public_hide_incident_details |
false |
Hides incident titles, timelines, and public comments on the public page. Hides incident history pages. Overall severity indicators remain visible. |
public_hide_maintenances |
false |
Hides scheduled and ongoing maintenance sections on the public page. Removes the maintenance history from incident history pages. |
Routing and Uptime Calculations
You can now specify whether specific incidents affect your service uptime. In the allquiet_routing resource, add exclude_from_uptime_calculation to your affects action block. The default value is false.
actions = {
add_interaction = "Affects"
affects_services = [allquiet_service.service.id]
exclude_from_uptime_calculation = true
}
Team and User Reporting
You can now manage weekly incident engagement report priorities via Terraform.
- Users: Use the
allquiet_userresource and setdisable_weekly_incident_engagement_reporttotrueorfalse. The default isfalse. - Teams: Use the
allquiet_teamresource and configureincident_engagement_report_settings.disable_weekly_incident_engagemen_reporttotrueorfalse. The default isfalse.
See the Terraform provider documentation and the Terraform Registry for resource details.
Updated August 11, 2026