ome_firmware_baseline (Resource)

This terraform resource is used to manage firmware baseline entity on OME.We can Create, Update and Delete OME firmware baseline using this resource. We can also do an ‘Import’ an existing ‘firmware baseline’ from OME .

Example Usage

/*
Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.
Licensed under the Mozilla Public License Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
    http://mozilla.org/MPL/2.0/
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

# Resource to manage a new firmware baseline
resource "ome_firmware_baseline" "firmware_baseline" {
  // Required Fields
  # Name of the catalog
  catalog_name = "tfacc_catalog_dell_online_1"
  # Name of the Baseline
  name = "baselinetest"
  
  // Only one of the following fields (device_names, group_names , device_service_tags) is required
  # List of the Device names to associate with the firmware baseline.
  device_names = ["10.2.2.1"]
  
  # List of the Group names to associate with the firmware baseline.
  # group_names = ["HCI Appliances","Hyper-V Servers"]
  
  # List of the Device service tags to associate with the firmware baseline.
  # device_service_tags = ["HRPB0M3"]
  
  // Optional Fields
  // This must always be set to true. The size of the DUP files used is 64 bits."
  #is_64_bit = true

  // Filters applicable updates where no reboot is required during create baseline for firmware updates. This field is set to false by default.
  #filter_no_reboot_required = true
  
  # Description of the firmware baseline 
  description = "test baseline"
}

Schema

Required

  • catalog_name (String) Name of the catalog
  • name (String) Name of the firmware baseline

Optional

  • description (String) Description of the firmware baseline
  • device_names (List of String) Device names is the list of device names that you want to add to the firmware baseline being created. One of DeviceNames or DeviceServiceTags or GroupNames is required
  • device_service_tags (List of String) Device service tags is the list of device service tags that you want to add to the firmware baseline being created.One of DeviceNames or DeviceServiceTags or GroupNames is required
  • filter_no_reboot_required (Boolean) Filters applicable updates where no reboot is required during create baseline for firmware updates.
  • group_names (List of String) Group names is the list of group names that you want to add to the firmware baseline being created.One of DeviceNames or DeviceServiceTags or GroupNames is required
  • id (Number) ID of the firmware baseline.
  • is_64_bit (Boolean) This must always be set to true. The size of the DUP files used is 64 bits.
  • last_run (String) Last Run Time for the firmware baseline
  • repository_name (String) Name of the repository

Read-Only

  • catalog_id (Number) ID of the catalog.
  • compliance_summary (Object) Compliance Summary (see below for nested schema)
  • downgrade_enabled (Boolean) Indicates if the firmware can be downgraded
  • repository_id (Number) ID of the repository. Derived from the catalog response
  • repository_type (String) Type of the repository
  • targets (Attributes List) The DeviceID, if the baseline is being created for devices or, the GroupID, if the baseline is being created for a group of devices. (see below for nested schema)
  • task_id (Number) Identifier of task which created this baseline.
  • task_status (String) Task status.

Nested Schema for compliance_summary

Read-Only:

  • compliance_status (String)
  • number_of_critical (Number)
  • number_of_downgrade (Number)
  • number_of_normal (Number)
  • number_of_unknown (Number)
  • number_of_warning (Number)

Nested Schema for targets

Required:

  • id (Number) ID of device associated with the firmware baseline.
  • type (Object) Type of device associated with the firmware baseline.. (see below for nested schema)

Nested Schema for targets.type

Read-Only:

  • id (Number)
  • name (String)

Import

Import is supported using the following syntax:

# Copyright (c) 2024 Dell Inc., or its subsidiaries. All Rights Reserved.

# Licensed under the Mozilla Public License Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at

#     http://mozilla.org/MPL/2.0/


# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# The command is
# terraform import ome_firmware_baseline.baseline <id>
# Example:
terraform import ome_firmware_baseline.baseline 6
# after running this command, populate the name field in the config file to start managing this resource