Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add upgrade guide for 1.10 #36019

Merged
merged 1 commit into from
Nov 18, 2024
Merged

docs: Add upgrade guide for 1.10 #36019

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 13 additions & 30 deletions website/docs/language/upgrade-guides/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,45 +1,28 @@
---
page_title: Upgrading to Terraform v1.9
description: Upgrading to Terraform v1.9
page_title: Upgrading to Terraform v1.10
description: Upgrading to Terraform v1.10
---

# Upgrading to Terraform v1.9
# Upgrading to Terraform v1.10

-> **Tip:** Use the version selector to view the upgrade guides for older Terraform versions.

Terraform v1.9 is a minor release in the stable Terraform v1.0 series.
Terraform v1.10 is a minor release in the stable Terraform v1.0 series.

Terraform v1.9 honors the
[Terraform v1.0 Compatibility Promises](https://developer.hashicorp.com/terraform/language/v1-compatibility-promises),
but there are two changes that may require additional upgrade steps:
Terraform v1.10 honors the
[Terraform v1.0 Compatibility Promises](https://developer.hashicorp.com/terraform/language/v1-compatibility-promises).
There are minor changes that may require additional upgrade steps:

- `.tftest.hcl` files no longer support the `version` attribute in the `provider` block.
- `import` blocks will now report an error if the `to` attribute points to a module that does not exist.
- `moved` blocks will now report an error if `from` or `to` points to a resource type conflicting with reserved keywords

See [the full changelog](https://github.com/hashicorp/terraform/blob/v1.9/CHANGELOG.md)
See [the full changelog](https://github.com/hashicorp/terraform/blob/v1.10/CHANGELOG.md)
for more details. If you encounter any problems during upgrading which are not
covered this guide, please start a new topic in
[the Terraform community forum](https://discuss.hashicorp.com/c/terraform-core)
to discuss it.

## Provider constraints in `.tftest.hcl` files
## Conflicting `moved` block references

In Terraform v1.9, the `version` attribute has been removed from the `provider`
block in the `.tftest.hcl` files. Terraform test files are not meant to be used
to specify provider versions, so this attribute has been removed to reflect the
intent of the test files.

If you are using the `version` attribute in the `provider` block in your test
files, you will need to remove it before running `terraform test` with Terraform
v1.9. Instead, you should update the `required_providers` block in your main
configuration to specify the provider version constraints.


## Invalid `import` blocks

In Terraform v1.9, the `import` block will now report an error if the `to`
attribute points to a module that does not exist. Previously, Terraform would
silently ignore these `import` blocks.

If you have `import` blocks that reference a module that does not exist, you
will need to update your configuration to remove or correct them.
Moved blocks now respect reserved keywords such as `local`, `each`, `self` etc. when parsing resource addresses.
Configurations that reference resources with type names that match top level blocks and
keywords from moved blocks will need to prepend the reference identifier with `resource.`.
Loading