Use Terraform to Provision Infrastructure on Linode Proposed Changes

Open

#7,479 opened on Jun 9, 2026 0 comments 0 reactions 1 assignee View on GitHub

@Rajakavitha1 is already working on this.

Since Jun 9, 2026.

Assessment

This issue has not been assessed yet.

The Terraform guide still uses region = "us-south" in its examples for Dallas, but the current Linode API returns Dallas as us-central.

Observed behavior:

Terraform config uses us-south
terraform apply succeeds
terraform state show later reports region = "us-central"
terraform plan then shows a diff from us-central -> us-south
attempting to apply may fail with:
Error: failed to migrate instance ... [400] [region] Cannot migrate linode to the same region

This suggests us-south is still accepted as a legacy alias, but us-central is now the canonical Dallas region ID returned by the API.

Request:
Please update the guide examples to use us-central for Dallas, TX to avoid perpetual Terraform drift and same-region migration errors.

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.