Cut Release 'v1.11.0'

Author: opslevel-ops

.changes/unreleased/added-campaign-resource.yaml

@@ -0,0 +1,3 @@
+## v1.11.0 - [May 20, 2026](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.10.1...v1.11.0)
+### Added
+* Added `opslevel_campaign` resource for managing OpsLevel campaigns as code, including scheduling support. Also added `opslevel_campaign` and `opslevel_campaigns` data sources.

.changes/v1.11.0.md

@@ -2,7 +2,9 @@
 All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and is generated by [Changie](https://github.com/miniscruff/changie).## v1.10.1 - [May 05, 2026](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.10.0...v1.10.1)
+and is generated by [Changie](https://github.com/miniscruff/changie).## v1.11.0 - [May 20, 2026](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.10.1...v1.11.0)
+### Added
+* Added `opslevel_campaign` resource for managing OpsLevel campaigns as code, including scheduling support. Also added `opslevel_campaign` and `opslevel_campaigns` data sources.## v1.10.1 - [May 05, 2026](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.10.0...v1.10.1)
 ### Fixed
 * Fixed `opslevel_service` dropping `preferred_api_document_source` after apply when `api_document_path` was not set, which caused a "Provider produced inconsistent result after apply" error## v1.10.0 - [April 21, 2026](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.9.1...v1.10.0)
 ### Fixed

CHANGELOG.md

@@ -1,4 +1,5 @@
 ---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "opslevel_campaign Data Source - terraform-provider-opslevel"
 subcategory: ""
 description: |-
@@ -9,17 +10,7 @@ description: |-
 
 Campaign data source
 
-## Example Usage
 
-```terraform
-data "opslevel_campaign" "example" {
-  identifier = "Z2lkOi8vb3BzbGV2ZWwvQ2FtcGFpZ24vMTIz"
-}
-
-output "campaign_name" {
-  value = data.opslevel_campaign.example.name
-}
-```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema
@@ -39,3 +30,5 @@ output "campaign_name" {
 - `start_date` (String) The start date of the campaign.
 - `status` (String) The current status of the campaign.
 - `target_date` (String) The target end date of the campaign.
+
+

docs/data-sources/campaign.md

@@ -1,4 +1,5 @@
 ---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "opslevel_campaigns Data Source - terraform-provider-opslevel"
 subcategory: ""
 description: |-
@@ -7,19 +8,9 @@ description: |-
 
 # opslevel_campaigns (Data Source)
 
-Campaign data sources — lists all campaigns, optionally filtered by status.
+Campaign data sources
 
-## Example Usage
 
-```terraform
-data "opslevel_campaigns" "active" {
-  status = "in_progress"
-}
-
-output "active_campaign_names" {
-  value = [for c in data.opslevel_campaigns.active.campaigns : c.name]
-}
-```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema
@@ -30,7 +21,7 @@ output "active_campaign_names" {
 
 ### Read-Only
 
-- `campaigns` (List of Object) List of Campaign data sources (see [below for nested schema](#nestedatt--campaigns))
+- `campaigns` (Attributes List) List of Campaign data sources (see [below for nested schema](#nestedatt--campaigns))
 
 <a id="nestedatt--campaigns"></a>
 ### Nested Schema for `campaigns`
@@ -46,3 +37,5 @@ Read-Only:
 - `start_date` (String) The start date of the campaign.
 - `status` (String) The current status of the campaign.
 - `target_date` (String) The target end date of the campaign.
+
+

docs/data-sources/campaigns.md

@@ -1,4 +1,5 @@
 ---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "opslevel_campaign Resource - terraform-provider-opslevel"
 subcategory: ""
 description: |-
@@ -9,12 +10,8 @@ description: |-
 
 Campaign Resource
 
-Manages an OpsLevel campaign. Campaigns allow you to roll out changes across your engineering organization that require orchestrated effort across multiple teams.
-
 ## Example Usage
 
-### Draft campaign (no schedule)
-
 ```terraform
 data "opslevel_team" "platform" {
   alias = "platform"
@@ -32,6 +29,9 @@ resource "opslevel_campaign" "upgrade_rails" {
   owner_id  = data.opslevel_team.platform.id
   filter_id = data.opslevel_filter.tier_1.id
 
+  start_date  = "2026-07-01"
+  target_date = "2026-09-30"
+
   project_brief = <<-EOT
     ## Overview
     All Rails services must upgrade to Rails 7 by end of Q3.
@@ -44,56 +44,6 @@ resource "opslevel_campaign" "upgrade_rails" {
 }
 ```
 
-### Campaign with checks
-
-```terraform
-resource "opslevel_campaign" "soc2_compliance" {
-  name      = "SOC2 Compliance Rollout"
-  owner_id  = data.opslevel_team.platform.id
-  filter_id = data.opslevel_filter.tier_1.id
-
-  check_ids = [
-    opslevel_check_custom_event.secret_rotation.id,
-    opslevel_check_custom_event.dependency_scanning.id,
-  ]
-
-  project_brief = <<-EOT
-    All Tier 1 services must pass SOC2 checks by end of Q3.
-  EOT
-}
-```
-
-### Scheduled campaign
-
-```terraform
-resource "opslevel_campaign" "python_upgrade" {
-  name      = "Upgrade to Python 3.12"
-  owner_id  = data.opslevel_team.platform.id
-  filter_id = data.opslevel_filter.tier_1.id
-
-  start_date  = "2026-07-01"
-  target_date = "2026-09-30"
-
-  project_brief = <<-EOT
-    Upgrade all Python services to 3.12 for security and performance.
-  EOT
-}
-```
-
-## Check Management
-
-The `check_ids` attribute accepts a list of rubric check IDs. On create, these checks are copied into the campaign. On update, the provider reconciles the list — adding new checks and removing stale ones to match the desired configuration.
-
-Terraform detects drift: if a check is removed from the campaign outside of Terraform (e.g. via the UI), the next `terraform plan` will show it as needing to be re-added.
-
-~> **Note:** The OpsLevel API copies checks into campaigns as separate instances with different IDs but the same name. The provider matches rubric checks to campaign checks by name. If two rubric checks share the same name, the provider may not be able to distinguish them, which can lead to incorrect removal. Ensure rubric check names are unique when using `check_ids`.
-
-## Schedule Management
-
-Setting both `start_date` and `target_date` schedules the campaign. Removing both fields unschedules it back to draft status.
-
-Both fields must be set together — setting only one will result in an error.
-
 <!-- schema generated by tfplugindocs -->
 ## Schema