Do not rush the materialize_source_webhook 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.

Context: Materialize terraform provider migration guide (materializeinc/terraform-provider-materialize docs/guides/materialize_source_table.md): The inline table block in source resources is deprecated in favor of separate materialize_source_table 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.