Terraform Provider for Dell - Redfish Release Notes 1.3.0


This release note contains supplemental information about Terraform Provider for Redfish.

Revision History

The table in this section lists the revision history of this document.

Revision Date History
01 September 2023 Terraform Provider 1.0.0 for Redfish
02 December 2023 Terraform Provider 1.1.0 for Redfish
03 March 2024 Terraform Provider 1.2.0 for Redfish
04 May 2024 Current release of Terraform Provider 1.3.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

  • Added Server Configuration Profile Resource
  • Added root user password update Resource


  • 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
  • Boot Order - Create, Read, Update
  • Boot Source Override - Read, Update
  • Manager Reset - Create, Read
  • Certificate - Create, Read, Delete
  • Lifecycle Controller Attributes - Read, Update
  • System Attributes - Read, Update
  • iDRAC Firmware Update - Update
  • Server Configuration Profile - Read, Update
  • User Password Update - Read, Update

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
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 In the current version, Terraform consistently relies on the state file for information during read refresh operations. This behavior is observed even if there have been changes to endpoint details, usernames, or passwords for a given rack. Users should be aware that, although updates can be made in the .tf file, Terraform will default to using the previously recorded details in the state file during any read refresh, whether it was initiated automatically or as a prerequisite to a planning operation. Whenever server connection configuration requires update , user has to manually change the the server block values (user, password, endpoint and ssl_insecure flag) in corresponding state file directly.
Storage volume resource attribute “optimum_io_size_bytes” value is updated from the server in case it is not provided in the terraform config “optimum_io_size_bytes” attribute of storage volume resource is optional and if it is not provided in the config (OR) if the value is given as null then during the subsequent run of ’terraform apply’ the system will show ‘update-in-place’ for “optimum_io_size_bytes” attribute as there is some default value set by the server. User should update the config with the value shown in plan i.e with the value present in terraform state
Use of validate_cert may not be supported under redfish v1.1.0 under certain circumstances. There are few examples of resources/datasources under terraform provider for RedFish v1.1.0 which specify use of ‘validate_cert’ inside provider block which is not supported. If you diagnose a issue saying ‘validate_cert’ is not supported, please replace that attribute with ‘ssl_insecure’ and inverse the boolean value if required. Also, you can refer to the examples in the provider documentation.


  • Virtual Media attribute “write_protected” can only be configured as “true”.


The software package is available for download from the Official Terraform Registry as well as from the Terraform Provider for Redfish GitHub page.



Product Guide