Changelog #

0.28.1 - 2026-09-13 #

Lockstep release with terradart_migrate 0.28.1 (passthrough emission fix — a bare Map / List parameter no longer comes out as TfArg.literal). No terradart_core API changes.

0.28.0 - 2026-09-13 #

Added #

TfArg.expression (TfArgExpression) — a raw Terraform expression, emitted verbatim as the tf.json template it is: TfArg.expression(r'${lower(var.name)}-x'), TfArg.expression<int>(r'${var.replicas * 2}'). Accepted on sensitive fields like TfArg.ref and TfArg.variable (no value is stored in it); the var.<name> references inside it are checked against the Stack's declarations at synth time; a plain value with no ${ ... } / %{ ... } sequence is rejected with an ArgumentError. Replaces the TfArg.literal(r'${...}') workaround. Breaking for exhaustive switches over TfArg — see MIGRATING.md (#662).
hasTemplateSequence / templateVariableNames — the template scanner behind it (escapes, quoted strings and directives handled), exported for tools that generate TfArg code.
Provider aliases — StackProvider.alias (provider "google" { alias = "eu" }), settable on every provider class in the workspace, and Resource.provider / Data.provider settable from every curated factory's new provider: parameter (provider: 'google.eu', or provider: 'google-beta' on a GA type). Synth emits provider.<name> as a list when a name has more than one configuration (Terraform's JSON form for aliases; a single default configuration keeps the object form) and rejects a provider: with no matching registration, the same name registered twice without an alias or with the same alias twice, and an alias that is not a Terraform identifier. Breaking for hand-written StackProvider implementations (one getter) — see MIGRATING.md (#666).
TfTimeouts / Resource.timeouts — the timeouts { ... } block as a Dart value (create, read, update, delete), on every curated factory and data source through the shared timeouts: parameter, emitted verbatim under the block's timeouts key. Provider-neutral like lifecycle: the values are the Go duration strings Terraform writes ('30m', '1h30m') — references are not allowed there — and which operations a type declares is terraform validate's business, not synth's. TfTimeouts.of(create: Duration(minutes: 30)) builds one from Durations; a value that is not a duration string throws (#671).
TfArg.workspace() — ${terraform.workspace}, the selected workspace's name, as a named argument instead of a hand-written expression. Sugar over TfArg.expression, so nothing about state layout or workspace selection changes (#671).
Partial backend configuration — every field of GcsBackend and S3Backend is optional, so a block whose values arrive at init time (terraform init -backend-config=bucket=...) is expressible: const GcsBackend() emits backend "gcs" {}. S3Backend.r2 keeps its endpoint and flag preset with bucket / key left out (#671).
ModuleCall / Stack.addModule — a module "<name>" { ... } call as a Dart value: source, version, inputs, providers, count / for_each and depends_on, emitted under the top-level module key in registration order. A module's outputs are read back as TfRefs (call.output<String>('member') → ${module.<name>.member}), so they flow into any TfArg slot, depends_on, lifecycle and exports. Synth validates what Terraform would: an input named like a meta-argument is rejected at construction, a providers value must name a registered provider configuration, and var.<name> references inside the inputs are checked like a resource's. A repeated local name throws DuplicateModuleError (#665).
A Stack that only calls modules needs no provider — Stack(providers: []) synthesizes when the stack registers at least one ModuleCall and no resource or data source of its own: the child modules pin what they use, so required_providers is omitted rather than empty. A stack with a resource still needs its provider (#665).
Stack.addMoved / TfMoved — moved { from = ... to = ... } blocks, emitted under the top-level moved key in registration order, so a renamed resource (or a count / for_each instance unrolled into its own resource) keeps its state. Registration rejects an empty or repeated from and from == to; synth rejects a to that names no resource of the Stack (a module. address passes) (#663).

Changed #

Sensitive nested fields accept any Terraform template — an unescaped ${ ... } or %{ ... } anywhere in the string — where they accepted only a string starting with ${ (#662).
SensitiveLiteralError — the recovery hint mentions TfArg.expression for values Terraform computes.

0.27.0 - 2026-08-30 #

Lockstep release across the workspace. Breaking — see MIGRATING.md.

Added #

S3Backend — terraform { backend "s3" { ... } } configuration, alongside the existing GcsBackend and LocalBackend. Covers S3 and the S3-compatible stores (Cloudflare R2, MinIO, Backblaze B2) via endpoints plus the skip_* flags. S3Backend.r2(accountId:, bucket:, key:) fills in the R2 endpoint, region = "auto", path-style addressing, and all five skip flags. Optional fields are omitted from the emitted JSON when null; an explicit false is emitted.
TfVariable + Stack.addVariable — declare the variable "<name>" { ... } blocks that TfArg.variable references. Synth emits them under the top-level variable key, and omits the key when a stack declares none (Terraform rejects an empty variable block).
Stack.addExternalVariable — accept TfArg.variable references to a variable declared in a hand-written file beside the generated main.tf.json, without emitting a block for it. For declarations TfVariable cannot model (validation { ... }) and for existing stacks that keep a variables.tf.
Undeclared-variable check at synth time — synth throws a StateError naming the variable and the resources referencing it when a TfArg.variable reference has no matching addVariable declaration, including references nested inside literal Maps and Lists. Previously such a config synthesised cleanly and failed at terraform plan with "Reference to undeclared input variable". Breaking — see MIGRATING.md.

Fixed #

Docs — Stack.backend and backends.dart described S3 as living in "provider-specific packages" and named an S3Backend that no package shipped. Both now describe what core actually provides.

Changed #

SensitiveLiteralError — the recovery hint now points at addVariable instead of telling the user to hand-write a variable block.

0.26.0 - 2026-08-24 #

Lockstep release with terradart_cloudflare 0.26.0 (catalog filled at the 5.23.0 pin). No terradart_core API changes.

0.25.3 - 2026-08-23 #

Lockstep release with terradart_appwrite 0.25.3 (catalog filled at the 2.0.0-beta.1 pin). No terradart_core API changes.

0.25.2 - 2026-08-22 #

Lockstep release with terradart_cloudflare 0.25.2 (initial release). No terradart_core API changes.

0.25.1 - 2026-08-19 #

Lockstep release with terradart_google_beta 0.25.1 (beta-only catalog filled). No terradart_core API changes.

0.25.0 - 2026-08-15 #

Lockstep release with terradart_google 0.25.0 (GA hashicorp/google catalog filled). No terradart_core API changes.

0.24.0 - 2026-07-03 #

Lockstep release with terradart_google 0.24.0 (typed nested helpers). No terradart_core API changes.

0.23.0 - 2026-07-02 #

Lockstep release. Breaking — see MIGRATING.md.

Breaking #

Removed the StackProvider.toTfJson() backwards-compat shim; read configArgs directly. Backend.toTfJson() / TfArg.toTfJson() are unchanged (real, distinct APIs).

0.22.0 - 2026-06-30 #

Lockstep release for Waves 76–77. No API changes in terradart_core.

0.21.0 - 2026-06-28 #

Lockstep release for Wave 74. No API changes in terradart_core.

0.20.0 - 2026-06-21 #

Lockstep release for Wave 73. No API changes in terradart_core.

0.19.0 - 2026-06-21 #

Lockstep release. No API changes vs 0.18.0.