Terraform provider v9.5.3: status_page select references non-existent column showEpisodeHistoryInDays #116

Closed
opened 2026-04-05 16:18:54 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @listellm on 2/6/2026

Description

The Terraform provider v9.5.3 (terraform-provider-oneuptime) includes showEpisodeHistoryInDays in the select clause when reading status_page resources. However, the OneUptime SaaS API does not yet recognise this column, resulting in a 400 error during terraform plan or terraform apply.

Steps to Reproduce

  1. Configure a oneuptime_status_page resource using provider version 9.5.3
  2. Run terraform plan or terraform apply
  3. The provider attempts to read the status page with a select clause that includes showEpisodeHistoryInDays

Error Output

Error: Parse Error

  with module.status_page["organization.project.customer"].oneuptime_status_page.this,
  on modules/status_page/status_page.tf line 1, in resource "oneuptime_status_page" "this":
   1: resource "oneuptime_status_page" "this" {

Unable to parse status_page response, got error: API request failed with
status 400: {"error":"Invalid select clause. Cannot select on
\"showEpisodeHistoryInDays\". This column does not exist on Status Page.
Here are the columns you can select on instead: _id, createdAt, updatedAt, ..."}

Root Cause

The provider v9.5.3 binary was generated from the OneUptime source that includes the "episode status page" feature (commit 82558fda59 Add episode management features to Status Page). The StatusPage model now includes showEpisodeHistoryInDays, and the auto-generated provider includes it in the select clause.

However, the production OneUptime SaaS at oneuptime.com has not yet been deployed with this schema migration, so the API rejects the select.

Verification

  • Confirmed showEpisodeHistoryInDays is present in the v9.5.3 provider binary via strings
  • Confirmed the column exists in the source at Common/Models/DatabaseModels/StatusPage.ts
  • Confirmed the migration exists at Common/Server/Infrastructure/Postgres/SchemaMigrations/1770237245069-MigrationName.ts
  • Provider v9.5.2 does not reference this column and works correctly

Workaround

Pin the provider to < 9.5.3:

oneuptime = {
  source  = "OneUptime/oneuptime"
  version = ">= 9.4.13, < 9.5.3"
}

Expected Resolution

Either:

  1. Deploy the episode feature (including the showEpisodeHistoryInDays column) to the OneUptime SaaS, or
  2. Release a patched provider version that does not select columns unavailable on the current SaaS API

Environment

  • Terraform: >= 1.14.0
  • OneUptime Provider: 9.5.3
  • Platform: Linux (amd64)
*Originally created by @listellm on 2/6/2026* ## Description The Terraform provider v9.5.3 (`terraform-provider-oneuptime`) includes `showEpisodeHistoryInDays` in the select clause when reading `status_page` resources. However, the OneUptime SaaS API does not yet recognise this column, resulting in a **400 error** during `terraform plan` or `terraform apply`. ## Steps to Reproduce 1. Configure a `oneuptime_status_page` resource using provider version `9.5.3` 2. Run `terraform plan` or `terraform apply` 3. The provider attempts to read the status page with a select clause that includes `showEpisodeHistoryInDays` ## Error Output ``` Error: Parse Error with module.status_page["organization.project.customer"].oneuptime_status_page.this, on modules/status_page/status_page.tf line 1, in resource "oneuptime_status_page" "this": 1: resource "oneuptime_status_page" "this" { Unable to parse status_page response, got error: API request failed with status 400: {"error":"Invalid select clause. Cannot select on \"showEpisodeHistoryInDays\". This column does not exist on Status Page. Here are the columns you can select on instead: _id, createdAt, updatedAt, ..."} ``` ## Root Cause The provider v9.5.3 binary was generated from the OneUptime source that includes the "episode status page" feature (commit `82558fda59 Add episode management features to Status Page`). The `StatusPage` model now includes `showEpisodeHistoryInDays`, and the auto-generated provider includes it in the select clause. However, the production OneUptime SaaS at `oneuptime.com` has not yet been deployed with this schema migration, so the API rejects the select. ## Verification - Confirmed `showEpisodeHistoryInDays` is present in the v9.5.3 provider binary via `strings` - Confirmed the column exists in the source at `Common/Models/DatabaseModels/StatusPage.ts` - Confirmed the migration exists at `Common/Server/Infrastructure/Postgres/SchemaMigrations/1770237245069-MigrationName.ts` - Provider v9.5.2 does **not** reference this column and works correctly ## Workaround Pin the provider to `< 9.5.3`: ```hcl oneuptime = { source = "OneUptime/oneuptime" version = ">= 9.4.13, < 9.5.3" } ``` ## Expected Resolution Either: 1. Deploy the episode feature (including the `showEpisodeHistoryInDays` column) to the OneUptime SaaS, or 2. Release a patched provider version that does not select columns unavailable on the current SaaS API ## Environment - Terraform: >= 1.14.0 - OneUptime Provider: 9.5.3 - Platform: Linux (amd64)
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#116