This document version is no longer actively maintained.
The site that you are currently viewing is an archived snapshot.
For up-to-date documentation, see the latest version.
Terraform Provider for Dell - Redfish Release Notes 1.1.0
Contents
This release note contains supplemental information about Terraform Provider for Redfish.
- Revision History
- Product Description
- New Features & Enhancements
- Known issues
- Limitations
- Distribution
- Documentation
Revision History
The table in this section lists the revision history of this document.
| Revision | Date | History |
|---|---|---|
| 01 | September 2023 | Current release of Terraform Provider 1.0.0 for Redfish |
| 02 | December 2023 | Current release of Terraform Provider 1.1.0 for Redfish |
Product Description
The Terraform Provider for Dell Technologies (Dell) RedFish allows data center and IT administrators to use Hashicorp Terraform to automate and orchestrate the provisioning and management of PowerEdge servers.
New Features & Enhancements
- Migrated to terraform-SDKv2-framework v2.27.0
- Added support for IPv6
Resources
- Bios - Read, Update
- Dell iDRAC Attributes - Read, Update
- System Power - Read, Update
- Simple Update - Read, Update
- Storage Volume - Create, Read, Update, Delete
- User Account - Create, Read, Update, Delete
- Virtual media - Create, Read, Update, Delete
- Manager reset - Create, Read, Update, Delete
- Virtual media - Create, Read, Update, Delete
- Virtual media - Create, Read, Update, Delete
Data Sources
- Bios - Read
- Dell iDRAC Attributes - Read
- Firmware Inventory - Read
- Storage Volume - Read
- System Boot - Read
- Virtual Media - Read
Known Issues
| Issue | Description | Workaround |
|---|---|---|
| State File Updated Despite Validation Errors | When using the custom Terraform provider, users may notice an unintended behavior during the terraform apply process. Even if the provider validation flags an error due to incorrect configuration and subsequently fails the apply operation, the state file gets updated (Ideally state file should not get updated). This issue is attributed to a known error in the Terraform SDKv2.(Link: https://github.com/hashicorp/terraform-plugin-sdk/issues/476) | If a user encounters a validation error, it is imperative to address and rectify the error in the configuration before proceeding with another terraform apply. This will ensure that the state remains consistent with the infrastructure. |
| Output is not displayed on console in datasource | Due to the presence of sensitive attribute (password) in the schema, the sensitive = true is added in output section of the data block due to which output is not displayed on console. |
Output can be checked in terraform state file. |
| The server details section in resources cannot be updated in a single scoop | Terraform always reads from state while performing a read refresh. Suppose your endpoint or username or password has changed for a rack. You can make the corresponding changes in the .tf file, but when terraform runs a read refresh (by itself or before a planning operation) the old details recorded in the state file will only be used. | Make sure that the previous server details are valid along with the new details while changing the configuration for the first time. Once the new details have been written to state, its safe to invalidate the previous details. |
Limitations
- Virtual Media attribute “write_protected” can only be configured as “true”.
- “capacity_bytes” and “volume_type” attributes of the storage volume cannot be updated.
Distribution
The software package is available for download from the Official Terraform Registry as well as from the Terraform Provider for Redfish GitHub page.