All Quiet Terraform Provider v3.0.0 is now available. This update introduces a breaking change to provide greater flexibility in how you manage users and their incident notification settings.

Key Benefits

• Decoupled Management: Separate user identity from notification preferences.

• Choice in Provisioning: Choose between fully managed setups or lightweight user creation where members configure their own settings.

• Granular Control: Manage notification rules as independent resources.

Breaking Change Overview

In version 3.0.0, we moved incident notification settings out of the allquiet_user resource. You must now use the new allquiet_user_incident_notification_settings resource to define how users receive alerts.

Required Action

You must update your Terraform configuration before your next deployment. If you upgrade the provider without updating your code, Terraform will fail because the old schema no longer exists.

Impact on Existing Users

This change only affects how Terraform manages configurations. It does not modify the settings of users you already provisioned. Their current notification rules remain active in the All Quiet platform.

Why We Made This Change

Version 3.0.0 allows you to decide how much control Terraform exerts over a user's experience.

1. Fully Managed Provisioning: Use both allquiet_user and allquiet_user_incident_notification_settings if you want to enforce specific phone numbers and notification rules.

2. Lightweight Provisioning: Use only allquiet_user. This creates the account and lets the team member set their own notification preferences within the All Quiet app later.

This separation simplifies the management of organizations with diverse notification needs.

Migration Guide

Follow these steps to upgrade to version 3.0.0:

1. Upgrade the Provider: Update your Terraform required_providers block to version 3.0.0.

2. Update User Resources: Remove the incident_notification_settings block from all allquiet_user resources.

3. Add Notification Resources: For users who require Terraform-managed settings, create a new allquiet_user_incident_notification_settings block. Link it to the user via the user ID.

4. Optional Self-Service: If you prefer new users to manage their own settings, omit the new notification resource for those specific accounts. For old users, you can also later delete allquiet_user_incident_notification_settings to allow self-management.

Example Migration

Before (v2.x.x):

resource "allquiet_user" "admin" {
  email = "[email protected]"
  incident_notification_settings {
    # old configuration here
  }
}

After (v3.0.0):

resource "allquiet_user" "admin" {
  email = "[email protected]"
}

resource "allquiet_user_incident_notification_settings" "admin_settings" {
  user_id = allquiet_user.admin.id
  # define notification rules here
}

If you need help with your specific configuration, contact our support team or refer to the technical documentation for detailed resource attributes.