Data Source: oci_fleet_software_update_fsu_cycles
This data source provides the list of Fsu Cycles in Oracle Cloud Infrastructure Fleet Software Update service.
Gets a list of all Exadata Fleet Update Cycles in a compartment.
Example Usage
data "oci_fleet_software_update_fsu_cycles" "test_fsu_cycles" {
#Required
compartment_id = var.compartment_id
#Optional
collection_type = var.fsu_cycle_collection_type
display_name = var.fsu_cycle_display_name
fsu_collection_id = oci_fleet_software_update_fsu_collection.test_fsu_collection.id
state = var.fsu_cycle_state
target_version = var.fsu_cycle_target_version
}
Argument Reference
The following arguments are supported:
collection_type- (Optional) A filter to return only resources whose Collection type matches the given type.compartment_id- (Required) The ID of the compartment in which to list resources.display_name- (Optional) A filter to return only resources that match the entire display name given.fsu_collection_id- (Optional) A filter to return only resources whose fsuCollectionId matches the given fsuCollectionId.state- (Optional) A filter to return only resources whose lifecycleState matches the given lifecycleState.target_version- (Optional) A filter to return only entries whose targetVersion matches the given targetVersion.
Attributes Reference
The following attributes are exported:
fsu_cycle_summary_collection- The list of fsu_cycle_summary_collection.
FsuCycle Reference
The following attributes are exported:
apply_action_schedule- Scheduling related details for the Exadata Fleet Update Action. The specified time should not conflict with existing Exadata Infrastructure maintenance windows. Null scheduleDetails would execute the Exadata Fleet Update Action as soon as possible.time_to_start- The date and time the Exadata Fleet Update Action is expected to start. RFC 3339, section 14.29.type- Type of scheduling strategy to use for Fleet Patching Update Action execution.
batching_strategy- Batching strategy details to use during PRECHECK and APPLY Cycle Actions.is_force_rolling- True to force rolling patching.is_wait_for_batch_resume- True to wait for customer to resume the Apply Action once the first half is done. False to automatically patch the second half.percentage- Percentage of availability in the service during the Patch operation.type- Supported batching strategies.
collection_type- Type of Collection this Exadata Fleet Update Cycle belongs to.compartment_id- Compartment Identifier.defined_tags- Defined tags for this resource. Each key is predefined and scoped to a namespace. Example:{"foo-namespace.bar-key": "value"}diagnostics_collection- Details to configure diagnostics collection for targets affected by this Exadata Fleet Update Maintenance Cycle.log_collection_mode- Enable incident logs and trace collection. Allow Oracle to collect incident logs and traces to enable fault diagnosis and issue resolution according to the selected mode.
display_name- Exadata Fleet Update Cycle display name.executing_fsu_action_id- OCID identifier for the Action that is currently in execution, if applicable.freeform_tags- Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example:{"bar-key": "value"}fsu_collection_id- OCID identifier for the Collection ID the Exadata Fleet Update Cycle is assigned to.goal_version_details- Goal version or image details for the Exadata Fleet Update Cycle.home_policy- Goal home policy to use when Staging the Goal Version during patching. CREATE_NEW: Create a new DBHome (for Database Collections) for the specified image or version. USE_EXISTING: All database targets in the same VMCluster or CloudVmCluster will be moved to a shared database home. If an existing home for the selected image or version is not found in the VM Cluster for a target database, then a new home will be created. If more than one existing home for the selected image is found, then the home with the least number of databases will be used. If multiple homes have the least number of databases, then a home will be selected at random.new_home_prefix- Prefix name used for new DB home resources created as part of the Stage Action. Format:_ If not specified, a default Oracle Cloud Infrastructure DB home resource will be generated for the new DB home resources created. software_image_id- Target database software image OCID.type- Type of goal target version specifiedversion- Target DB or GI version string for the Exadata Fleet Update Cycle.
id- OCID identifier for the Exadata Fleet Update Cycle.is_ignore_missing_patches- List of bug numbers to ignore.is_ignore_patches- Ignore all patches between the source and target homes during patching.is_keep_placement- Ensure that services of administrator-managed Oracle RAC or Oracle RAC One databases are running on the same instances before and after the move operation.last_completed_action- The latest Action type that was completed in the Exadata Fleet Update Cycle. No value would indicate that the Cycle has not completed any Action yet.lifecycle_details- A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.max_drain_timeout_in_seconds- Service drain timeout specified in seconds.next_action_to_execute- In this array all the possible actions will be listed. The first element is the suggested Action.time_to_start- The date and time the Exadata Fleet Update Action is expected to start. Null if no Action has been scheduled. RFC 3339, section 14.29.type- Type of Exadata Fleet Update Action
stage_action_schedule- Scheduling related details for the Exadata Fleet Update Action. The specified time should not conflict with existing Exadata Infrastructure maintenance windows. Null scheduleDetails would execute the Exadata Fleet Update Action as soon as possible.time_to_start- The date and time the Exadata Fleet Update Action is expected to start. RFC 3339, section 14.29.type- Type of scheduling strategy to use for Fleet Patching Update Action execution.
state- The current state of the Exadata Fleet Update Cycle.system_tags- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:{"orcl-cloud.free-tier-retained": "true"}time_created- The date and time the Exadata Fleet Update Cycle was created, as described in RFC 3339, section 14.29.time_finished- The date and time the Exadata Fleet Update Cycle was finished, as described in RFC 3339.time_updated- The date and time the Exadata Fleet Update Cycle was updated, as described in RFC 3339, section 14.29.type- Type of Exadata Fleet Update Cycle.