2.0.0 (March 30, 2026)

Key Takeaway - What You Need to Know

Nothing changes for you! This release adds internal support for Terraform's Plugin Framework alongside our existing implementation. All your existing Terraform configurations work exactly as before with zero changes required.

Why Version 2.0.0?

We're bumping to v2.0.0 to signal an important internal architectural enhancement: the provider now supports Terraform Plugin Framework in addition to the existing SDKv2 implementation. This is a major milestone that enables future capabilities while maintaining complete backward compatibility.

What This Means for You

For Existing Users:

✅ All your existing resources and data sources work unchanged
✅ No modifications needed to your Terraform configurations
✅ No breaking changes whatsoever
✅ Your state files remain fully compatible
✅ Simply update the version and continue as normal

For New Users:

✅ Same great provider experience
✅ Access to all IBM Cloud services
✅ Future-ready architecture

What Changed Internally

The provider now runs two implementations side-by-side using terraform-plugin-mux:

SDKv2 Provider (existing) - Handles all current resources and data sources
Plugin Framework Provider (new) - Enables next-generation features

This dual architecture is completely transparent to you. The provider automatically routes requests to the appropriate implementation.

Why Add Plugin Framework Support?

The Plugin Framework enables us to deliver future enhancements:

Terraform Actions - Imperative operations on resources (requires Terraform 1.10+)
Better Type Safety - Improved handling of complex nested structures
Enhanced Validation - More expressive validation rules
Improved Error Messages - Clearer diagnostics and actionable guidance
Modern Features - Access to latest Terraform capabilities

Upgrading from v1.x

Step 1: Update Your Version Constraint

terraform {
  required_providers {
    ibm = {
      source  = "IBM-Cloud/ibm"
      version = "~> 2.0.0"  # Changed from "~> 1.89.0"
    }
  }
}

Step 2: Upgrade the Provider

terraform init -upgrade

Step 3: Verify (Optional)

terraform plan

You should see no changes - everything works exactly as before!

What's Next?

In future releases, we'll gradually:

Introduce new resources using the Plugin Framework
Migrate existing resources where it provides clear benefits (depending on the requirements)
Implement Actions for resources that benefit from imperative operations
Continue improving the provider experience

All changes will be backward compatible and clearly documented.

FAQ

Q: Do I need to change my Terraform configurations?
A: No! Everything works exactly as before.

Q: Will my state files still work?
A: Yes, state files are fully compatible.

Q: Is this a breaking change?
A: No, this release has zero breaking changes. We're using v2.0.0 to signal the architectural enhancement.

Q: Why bump to v2.0.0 if nothing breaks?
A: To clearly communicate this significant internal milestone and set expectations for future framework-based enhancements.

Q: Can I rollback if needed?
A: Yes, simply change the version constraint back to ~> 1.89.0 and run terraform init -upgrade.

Q: When will I see new features from the Plugin Framework?
A: New capabilities will be introduced incrementally in upcoming 2.x releases.

Support

Documentation: https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs
GitHub Issues: https://github.com/IBM-Cloud/terraform-provider-ibm/issues
IBM Cloud Support: https://cloud.ibm.com/unifiedsupport/supportcenter

Summary

Version 2.0.0 is an internal architectural enhancement that adds Plugin Framework support while maintaining 100% backward compatibility. Your existing Terraform configurations work unchanged - simply update the version constraint and continue managing your IBM Cloud infrastructure as you always have.

- The IBM Cloud Terraform Provider Team

Notes :

Bug Fixes

Power Systems: CCNA Error Msg Refactor (#6711)
Power Systems: Capture Error Msg Refactor (#6712)
VPC Infrastructure: Update size validation range for RFS (#6709)
General: Fix the missing read env for provider (#6704)
VPC Infrastructure: fixed document for is_images datasource (#6689)
Transit Gateway: handle create timeout by checking existing connec… (#6703)
Cloud Internet Services: handle null timestamps in CIS custom page resource (#6702)
Cloud Logs: add Computed to alert filter_type and incident_settings fields (#6716)
Partner Center Sell: Add id to composite children plan updatable flag is editable parnercentersellv1 (#6698)

Enhancements

Code Engine: Add ibm_code_engine_build_run action with Plugin Framework support (#6611)
Power Systems: Add externalIP attribute for network_interface (#6705)
Power Systems: Add Asaps To SAP Profile/s (#6708)
Cloud Databases: Refactor ibm_database resource and datasource to introduce backend abstraction (#6667)
Transit Gateway: support Secrets Manager CRNs in authentication_key (#6713)
Cloud Logs: Logs Routing Default Private CSE endpoint and write_status (#6710)
Cloud Logs: Update Views API for PR #164 (#164)
Secrets Manager: Private path support for Code Engine (#6699)
Configuration Aggregator: Add IBM Account Management API Support (#6701)
Cloud Logs: Add IBM Cloud Logs Extensions API support (#6700)
Secrets Manager: SM event notification datasource should not fail when no registration exists (#6692)

IBM-Cloud/terraform-provider-ibm v2.0.0 on GitHub