Konstruct 0.6.5

Released: July 2026

Highlights

• Per-deployment Terraform module folders — each IaC deployment now gets its own terraform/{deployment-name} folder in the GitOps repository, so deployments of the same module no longer overwrite each other
• Fixed: duplicate IaC deploy inputs — a provider file token and a variables.tf variable that share a name (for example <CLUSTER_NAME> and cluster_name) are now treated as one variable, so the deploy form shows a single input instead of two

Per-deployment Terraform module folders

Deploying an IaC catalog item copies the Terraform module into your GitOps repository. Previously every deployment of the same module wrote into one shared terraform/ folder, so a second deployment overwrote the files of the first — two instances of the same module could not coexist.

Each deployment now gets its own folder, named after the deployment:

terraform/
  my-first-bucket/     # deployment "my-first-bucket"
  my-second-bucket/    # deployment "my-second-bucket"

Deployments of the same module are fully independent: creating, updating, or deleting one never touches the files of another. Existing deployments are unaffected — the new layout applies to deployments created on 0.6.5 or later.

Changed again in 0.6.7

0.6.7 removes the copy step entirely — the Crossplane Workspace references the Terraform module directly at its source repository, so nothing is copied into the GitOps repository at all. If you are upgrading now, read the 0.6.7 patch notes for the behavior you end up with.

Fixed: duplicate IaC deploy inputs

An IaC catalog item can name the same value twice: once as a token in the provider file (for example <CLUSTER_NAME>) and once as a variable in variables.tf (cluster_name). The deploy form treated these as two unrelated inputs and asked for the value twice — and nothing kept the two answers consistent.

Names are now normalized before the form is built, so a provider token and a variables.tf variable that differ only in case and format — CLUSTER_NAME and cluster_name — resolve to the same variable. The deploy form shows a single input, and the value you enter is applied to both the provider file token and the Terraform variable.

Catalog items whose provider tokens and variables never overlapped are unaffected.

Upgrade notes

Update the targetRevision in your platform team's Konstruct Argo CD Application manifest to 0.6.5:

spec:
  source:
    chart: konstruct
    repoURL: oci://europe-west2-docker.pkg.dev/civo-com/charts
    targetRevision: 0.6.5

Commit and push — Argo CD syncs the new version automatically. No manual migration steps are required.

• Existing IaC deployments keep their current folder. Only deployments created on 0.6.5 or later use per-deployment folders.

What's next?

• Create an IaC catalog item — provider tokens and Terraform variables explained
• Deploy a catalog item — the deploy form and its inputs
• Provision an environment from the catalog — catalog items in environment workflows