Releases: IBM-Cloud/terraform-provider-ibm
v2.0.2
v2.0.1
2.0.1 (April 14, 2026)
Bug Fixes
- Cloud Logs: fix syntax type plan change (#6725)
- Configuration Aggregator: Have single source of truth for ICR urls (#6739)
- Transit Gateway: [TGW] Add documentation for default_prefix_filter (#6734)
- Power Systems: Fix-pi route next hop update (#6741)
Enhancements
- General: bump goreleaser/goreleaser-action from 6 to 7 (#6679)
- General: bump google.golang.org/grpc from 1.79.2 to 1.79.3 (#6731)
- Container Registry: Pull in latest icr SDK version (#6729)
- Event Notification: Support for bounce metrics Data source and metrics, subscription-id filter for metrics (#6594)
- General: bump crazy-max/ghaction-import-gpg from 6.1.0 to 7.0.0 (#6727)
- General: bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 (#6730)
v2.0.0
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 -upgradeStep 3: Verify (Optional)
terraform planYou 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)
v1.89.0
1.89.0 (March 2, 2026)
Bug Fixes
- CIS: Fixed mTLS empty hostnames issue (#6669)
- Global Tagging: Fixed tagging error (#6681)
- Activity Tracker: Removed redundant checks to fix build on Go 1.26 (#6682)
- Cloud Databases: Added nil check on response in
ibm_databaseresource (#6660)
Enhancements
- CD Tekton Pipeline: Fixed multiline properties handling (#6680)
- Cloud Object Storage: Updated documentation for COS cross-account access (#6685)
- IAM: Terraform no longer plans an update-in-place when no resources exist for a template assignment (#6664)
- Power Systems: Refactored host group update logic (#6677)
- Toolchain: Added region discontinuation warnings for Continuous Delivery (CD) (#6687)
v1.88.3
v1.88.2
v1.88.1
v1.88.0
1.88.0 (February 6, 2026)
Bug Fixes
- Catalog Management: fix import of ibm_cm_offering (#6636)
- Cloud Logs: change inclusion_filters to optional (#6649)
- IAM: Fix policy creation when resourceType is set to 'resource-group' (#6621)
Enhancements
- Code Engine: add support for code engine pds, hmac secrets and trusted profiles (#6610)
- Schematics: extend template type validation regex (#6593)
- Cloud Databases: Add
async_restorefield for fast PG restore (#6630) - Cloud Logs: add terraform support for logs router v3 (#6627)
- IAM: add api key expiration field (#6640)
- Platform Notifications: Platform Notification Distribution List API: Terraform support (#6628)
- Power Systems: Update DHCP status check for polling (#6642)
- VPC Infrastructure: Added an empty check on allowed_use for is_instance and is_volume (#6631)
- VPC Infrastructure: added support for spot virtual server instances (#6637)
- VPC Infrastructure: add network-bandwidth-mode support (#6648)
- General: Update MR in-che endpoint (#6647)