Migrating Materialize webhook sources is a rebuild, not an upgrade

Migrating Materialize webhook sources is a rebuild, not an upgrade

TL;DR

Do not rush the materializesourcewebhook migration. There is no automated path on the database side, so the recommended move is to stay on the legacy resource until one exists. If you recreate instead, plan for total data loss on the webhook, downtime while you rebuild, and new endpoint URLs that force updates to every downstream view.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Treat this as a rebuild with a maintenance window, not an in-place upgrade.

Context: Materialize terraform provider migration guide (materializeinc/terraform-provider-materialize docs/guides/materializesourcetable.md): The inline table block in source resources is deprecated in favor of separate materializesourcetable resources, and there is no automated migration on the database side. Option 1 is to wait for the automated path while the legacy resource stays supported. Option 2, recreating with the new resource, costs all existing webhook data, downtime during recreation, and new endpoint URLs that downstream views must be repointed at.

Materialize terraform provider migration guide (materializeinc/terraform-provider-materialize docs/guides/materializesourcetable.md): The inline table block in source resources is deprecated in favor of separate materializesourcetable resources, and there is no automated migration on the database side. Option 1 is to wait for the automated path while the legacy resource stays supported. Option 2, recreating with the new resource, costs all existing webhook data, downtime during recreation, and new endpoint URLs that downstream views must be repointed at. Resolved: Do not rush the materializesourcewebhook migration. There is no automated path on the database side, so the recommended move is to stay on the legacy resource until one exists. If you recreate instead, plan for total data loss on the webhook, downtime while you rebuild, and new endpoint URLs that force updates to every downstream view. Treat this as a rebuild with a maintenance window, not an in-place upgrade. Source: https://github.com/materializeinc/terraform-provider-materialize/blob/HEAD/docs/guides/materializesourcetable.md