Skip to content
Merulan

Infrastructure as Code

Install the signed Merulan provider, inspect its schema, and prepare reviewed OpenTofu changes.

Infrastructure as Code is how teams use OpenTofu with Merulan. It puts each planned change in a file that a team can review.

Public acquisition: Available. OpenTofu can install registry.terraform.io/merulan-org/merulan version 0.1.0. Anonymous installation verified signature key 8E4AAC4BBF17C6CB, loaded the provider schema, and validated a configuration on September 17, 2026. For TypeScript, use Merulan CDK.

Authenticated plan, apply, drift, upgrade, and authoritative readback are Preview. They have not been qualified since the production infrastructure was hibernated.

License: PolyForm Shield 1.0.0. Support: support@merulan.com. Security reports: security@merulan.com.

Set up access

Infrastructure as Code setup starts by pinning the provider version in required_providers, then running tofu init. For live use after qualification, set its API base_url and secret token. Set default_workspace_id only when a resource may use one default Workspace. A Workspace set on the resource still wins. A token must not enter state or logs.

Do not use a local binary, development override, or private source as a public install path.

How the Infrastructure as Code works

The provider calls the Merulan HTTP API. Its resources and data sources turn OpenTofu settings into API calls. They do not connect to Merulan storage. Management authority decides who may change Workspace design.

Use the OpenTofu reference for each resource and data source. The API (HTTP) reference owns the HTTP calls. Each Surface keeps its own syntax.

First call

After release, start with the provider and one read-only data source from the OpenTofu reference. Run a plan. Check the Workspace id and each proposed change before apply. Read the remote object again and compare it with the Console.

For Product installs, Build, install, and recover owns the life cycle. Provider syntax does not change it.

When it fails

Infrastructure as Code settings are invalid

Check the base_url, secret token, and Workspace. Fix the settings before you plan again.

Live operation is unavailable

Public installation and offline validation remain available. Do not plan or apply against production until live qualification is published.

A change is refused

The provider calls the API, so the API decides the change. Read the refusal and the Workspace it names. Check that the Workspace is the one you meant. Management authority owns who may change Workspace design. Do not widen a token to pass the check.

Reference