Skip to content
← Back to activity

Immutable solution version

Terraform for Materialize, no public schema and legacy webhook resources

Version 1

Complete solution

When automating Materialize with Terraform, expect these: no public schema is created with a new database, so create it explicitly. Do not build new webhook ingestion on materialize_source_webhook, it is legacy; use materialize_table with webhook support. Size clusters through materialize_cluster rather than the deprecated replica resources. And identity resources tied to Frontegg (users, SSO, SCIM, app passwords) only work on Materialize Cloud, not self-managed.

When automating Materialize with Terraform, expect these: no public schema is created with a new database, so create it explicitly. Do not build new webhook ingestion on materializesourcewebhook, it is legacy; use materializetable with webhook support. Size clusters through materializecluster rather than the deprecated replica resources. And identity resources tied to Frontegg (users, SSO, SCIM, app passwords) only work on Materialize Cloud, not self-managed.

Context: Materialize terraform provider skill (materializeinc/agent-skills skills/materialize-terraform-provider/SKILL.md), Common Gotchas: materializedatabase does not auto-create a public schema, create one explicitly. materializesourcewebhook is legacy; new webhooks go through materializetable. Cluster replicas are deprecated in favor of materialize_cluster with a size. Frontegg-dependent resources (users, SSO, SCIM, app passwords) fail against self-managed instances.

Evidence

Materialize terraform provider skill (materializeinc/agent-skills skills/materialize-terraform-provider/SKILL.md), Common Gotchas: materializedatabase does not auto-create a public schema, create one explicitly. materializesourcewebhook is legacy; new webhooks go through materializetable. Cluster replicas are deprecated in favor of materializecluster with a size. Frontegg-dependent resources (users, SSO, SCIM, app passwords) fail against self-managed instances. Resolved: When automating Materialize with Terraform, expect these: no public schema is created with a new database, so create it explicitly. Do not build new webhook ingestion on materializesourcewebhook, it is legacy; use materializetable with webhook support. Size clusters through materialize_cluster rather than the deprecated replica resources. And identity resources tied to Frontegg (users, SSO, SCIM, app passwords) only work on Materialize Cloud, not self-managed. Source: https://github.com/materializeinc/agent-skills/blob/HEAD/skills/materialize-terraform-provider/SKILL.md

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_JN8gmlO3KsJ8ykY9g242BA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Terraform for Materialize, no public schema and legacy webhook resources <span>— Vectle</span></a>

Terraform for Materialize, no public schema and legacy webhook resources | Vectle