Terraform version support and deprecation lifecycle
Schematics service supports Terraform_v1.5.7. It is advisable to always upgrade to the current Terraform release supported by Schematics. For compliance and security considerations, remain on a Terraform release with HashiCorp Configuration
Language (HCL) provided maintenance and security fixes. For more information about Terraform fix support, Schematics end of marketing dates for Terraform releases, and end of support, see the deprecation schedule.
The Terraform_v1.4.6 is deprecated, but the creation and execution of workspace by using this version is still allowed. For more information, see Deprecation schedule.
For more information about updating Terraform release, see Upgrading the Terraform workspace version. Terraform v1.0 was a major release for Terraform,
marking the transition to a stable 1.x release. HCL made compatibility promises for the 1.x releases, for the core Terraform features and
function. No changes needed to HCL templates to upgrade through the 1.x releases.
Schematics Terraform deprecation lifecycle
The table outlines the timetable of support that is provided by Schematics for Terraform releases. For more information about the maintenance and fixes, see the following sections.
| Timescale | Schematics operations |
Terraform Maintenance and security fixes | Upgrade |
|---|---|---|---|
| 0-6 months | Full operations | Yes | Suggested |
| 6-12 months | Full operations | No | Suggested. Upgrade if Terraform fix needed. |
| 12 - 24 months | Workspace creation restricted | No | Suggested. Upgrade if Terraform fix needed. |
| 24 months | Workspace execution restricted | No | Needed |
Terraform maintenance and fixes
Schematics supports Terraform releases in line with Terraform support and end-of-life policy. Schematics always supports at least one Terraform release with maintenance and security fix support.
After the end of Terraform maintenance and security fixes, Schematics maintains full operational support for 24 months from release GA. If an issue is identified in Terraform that requires a fix, the user is required to update to a release with current maintenance and security fixes.
After end of Terraform maintenance Schematics moves to supporting operations with the final point (fix pack) Terraform release.
The deprecation and use of each Terraform version in Schematics follows the following phases.
Restrict workspace creation
After 12 months from GA, users cannot create new Schematics workspaces with this release. Existing workspaces and resources by using the release can continue to be managed by using the release. It is suggested to update to the current supported Terraform release.
During this time Schematics supports only operations with the final point (fix pack) Terraform release.
Restrict workspace execution
After 24 months from GA, users no longer be able to manage IBM Cloud resources with IBM Cloud Schematics workspaces by using this release. The workspace must first be updated to use a release of Terraform with HCL provided maintenance and security fixes. The content of the workspaces remains accessible and the Terraform release can be updated in Schematics to re-enable operations.
If you choose not to upgrade to the current version of Terraform beyond the restrict workspace execution date:
- Your Schematics workspace data continues to stay in Schematics until you delete these workspaces.
- You cannot do operations on, or destroy the IBM Cloud resources by using Schematics. The resources can still be deleted through the IBM Cloud console or CLI.
Deprecation Schedule
You are suggested always to migrate from your in use version of Terraform to the current available version and to remain on Terraform versions with maintenance and security fixes. You can see the current in use version of Terraform in the drop down list of the Schematics workspace configuration page.
Schematics announces the timeline for the deprecation of Terraform versions, the related end of marketing date, and end of support date when you are using the IBM Cloud Schematics service. The month that is provided in the table represents the last day of the Month to restrict workspace creation and execution. The deprecation timeline changes as new Terraform versions are released.
| Versions | Terraform end of maintenance and security support | Phase 1: Restrict workspace creation (End of marketing) |
Phase 2: Restrict workspace execution (End of support) |
|---|---|---|---|
| Terraform v0.x | 2021 and earlier | May 2022 | September 2023 |
| Terraform v0.15 | July 2021 | September 2023 | September 2024 |
| Terraform v1.0 | May 2022 | September 2023 | September 2024 |
| Terraform v1.1 | September 2022 | September 2023 | September 2024 |
| Terraform v1.2 | March 2023 | March 2024 | March 2025 |
| Terraform v1.3 | End of December 2023 | April 2024 | Earliest July 2025 |
| Terraform v1.4 | End of December 2023 | Earliest September 2024 | Earliest September 2025 |
User actions
Follow these steps to upgrade to continue working with the latest versions of Terraform in IBM Cloud Schematics.
-
Identification: Identify the version of Terraform in your IBM Cloud Schematics workspaces. The Schematics workspace list indicates the version Terraform in use. Also, the individual Schematics workspace settings pages in the console indicate the version of Terraform configured for use with the workspace. If you are using the command-line run
ibmcloud schematics workspace listcommand to show the Terraform version. -
Migration: Migrating older Terraform versions to the current supported version. For more information about migrating Terraform versions, see Upgrading the Terraform workspace version.
-
Verification: You can verify that a workspace has been migrated and is functional by performing a test operation. From the CLI you can run a
ibmcloud schematics refreshoribmcloud schematics plancommands to verify that jobs for the the migrated workspace execute successfully.
Now you are at a current version of Terraform, and can continue using the IBM Cloud Schematics workspaces.