| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2025-11-25 |
terraform version deprecation, deprecation, terraform support schematics |
schematics |
{{site.data.keyword.attribute-definition-list}}
{: #deprecate-tf-version}
{{site.data.keyword.bpshort}} service supports Terraform_v1.4.6, Terraform_v1.5.7, Terraform_v1.6.6, Terraform_v1.7.5, Terraform_v1.8.5, Terraform_v1.9.2, Terraform_v1.10.5, Terraform_v1.11, Terraform_v1.12. Terraform_v1.9.2 is set as default version.
{{site.data.keyword.bpshort}} announces to support Terraform v1.13.4 and keep Terraform v1.12 as the default version from 08 December 2025. Additionally, the restriction and end of marketing on {{site.data.keyword.bpshort}} workspace creation for Terraform versions v1.7 and v1.8 effective from 28 January 2026. For more information about supported versions and the deprecation of workspace creation and executions, see the Deprecation schedule.
{: important}
It is advisable to always upgrade to the current Terraform release supported by {{site.data.keyword.bpshort}}. 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, {{site.data.keyword.bpshort}} end of marketing dates for Terraform releases, and end of support, see the deprecation schedule.
For more information about updating the 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 that are needed to HCL templates to upgrade through the 1.x releases.
{: shortdesc}
{: #deprecate-phase}
The table outlines the timetable of support that is provided by {{site.data.keyword.bpshort}} for Terraform releases. For more information about the maintenance and fixes, see the following sections.
Timescale |
{{site.data.keyword.bpshort}} Functions |
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 |
| {: caption="Deprecation lifecycle" caption-side="top"} |
{: #deprecate-maintenance}
{{site.data.keyword.bpshort}} supports Terraform releases in line with Terraform support and end-of-life policy{: external}. {{site.data.keyword.bpshort}} always supports at least one Terraform release with maintenance and security fix support.
After the end of Terraform maintenance and security fixes, {{site.data.keyword.bpshort}} 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 the latest maintenance and security fixes.
After the end of Terraform maintenance {{site.data.keyword.bpshort}} moves to supporting operations with the final point (fix pack) Terraform release.
The deprecation and use of each Terraform version in {{site.data.keyword.bpshort}} follows the following phases.
{: #deprecate-wks-create}
After 12 months from GA, users cannot create new {{site.data.keyword.bpshort}} 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 the current supported Terraform release.
During this time {{site.data.keyword.bpshort}}, supports only operations with the final point (fix pack) Terraform release.
{: #deprecate-wks-execute}
After 24 months from GA, users will no longer be able to manage Cloud resources with {{site.data.keyword.bplong_notm}} 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 {{site.data.keyword.bpshort}} to re-enable operations.
If you choose not to upgrade to the latest Terraform version before the restrict workspace execution date:
- Your {{site.data.keyword.bpshort}} workspace data continues to stay in {{site.data.keyword.bpshort}} until you delete these workspaces.
- You cannot do operations on, or destroy the Cloud resources by using {{site.data.keyword.bpshort}}. The resources can still be deleted through the {{site.data.keyword.cloud_notm}} console or CLI.
{: #deprecate-timeline}
You are suggested always to migrate from your in-use version of Terraform to the currently available version and to remain on Terraform versions with maintenance and security fixes. You can see the current version of Terraform in the drop-down list of the {{site.data.keyword.bpshort}} workspace configuration page. {: shortdesc}
{{site.data.keyword.bpshort}} 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 {{site.data.keyword.bplong_notm}} 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 support | Terraform end of maintenance and security support | Phase 1: Restrict workspace creation ( End of marketing) |
Phase 2: Restrict workspace execution ( End of support) |
|---|---|---|---|---|
| Terraform v1.13 | 08 December 2025 | 30 May 2027 | 31 November 2027 | 29 May 2027 |
| Terraform v1.12 | 31 July 2024 | 30 January 2026 | 31 July 2026 | 29 January 2027 |
| Terraform v1.11 | 31 July 2024 | 30 January 2026 | 31 July 2026 | 29 January 2027 |
| Terraform v1.10 | 30 May 2024 | 30 December 2025 | 30 June 2026 | 29 January 2027 |
| Terraform v1.9 | 21 August 2024 | 30 May 2025 | 28 February 2026 | 31 August 2026 |
| Terraform v1.8 | 21 August 2024 | 30 May 2025 | 28 January 2026 | 31 July 2026 |
| Terraform v1.7 | 21 August 2024 | 30 May 2025 | 28 January 2026 | 31 July 2026 |
| Terraform v1.6 | 5 June 2024 | 16 December 2024 | 15 July 2025 | 15 January 2026 |
| Terraform v1.5 | 6 September 2023 | 31 October 2024 | 31 December 2024 | 30 September 2025 |
| Terraform v1.4 | July 2023 | 30 September 2024 | 31 December 2024 | 30 September 2025 |
| Terraform v1.3 | Deprecated | End of December 2023 | April 2024 | 31 July 2025 |
| Terraform v1.2 | Deprecated | March 2023 | March 2024 | 31 March 2025 |
| Terraform v1.1 | Deprecated | September 2022 | September 2023 | 30 September 2024 |
| Terraform v1.0 | Deprecated | May 2022 | September 2023 | 30 September 2024 |
| Terraform v0.15 | Deprecated | July 2021 | September 2023 | 30 September 2024 |
| Terraform v0.14 | Deprecated | 2021 and earlier | May 2022 | 30 September 2024 |
| Terraform v0.13 | Deprecated | 2021 and earlier | May 2022 | 30 September 2024 |
| Terraform v0.12 | Deprecated | 2021 and earlier | May 2022 | September 2021 |
| Terraform v0.11 | Deprecated | 2021 and earlier | May 2022 | September 2021 |
| {: caption="Deprecation timeline" caption-side="top"} |
{: #user-action}
Following are the steps to continue by using the current Terraform versions in {{site.data.keyword.bplong_notm}}.
Identification
: Identify the version of Terraform in your {{site.data.keyword.bplong_notm}} workspaces. The {{site.data.keyword.bpshort}} workspace list indicates the version Terraform in use. Also, the individual {{site.data.keyword.bpshort}} 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 list command to show the Terraform version.
Migration : Migration of older Terraform releases to the currently supported version. For more information about migrating the Terraform version, see Upgrading the Terraform workspace version.
Verification
: You can verify that a workspace is migrated and is functional by test operation. From the CLI, you can run a ibmcloud schematics refresh or ibmcloud schematics plan commands to verify that jobs for the migrated workspace run successfully.
Now you are at a current version of Terraform, and can continue by using the {{site.data.keyword.bplong_notm}} workspaces.