Oracle Cloud Infrastructure v2.33.0 published on Thursday, May 1, 2025 by Pulumi
oci.Database.getMaintenanceRun
Explore with Pulumi AI
This data source provides details about a specific Maintenance Run resource in Oracle Cloud Infrastructure Database service.
Gets information about the specified maintenance run.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testMaintenanceRun = oci.Database.getMaintenanceRun({
    maintenanceRunId: testMaintenanceRunOciDatabaseMaintenanceRun.id,
});
import pulumi
import pulumi_oci as oci
test_maintenance_run = oci.Database.get_maintenance_run(maintenance_run_id=test_maintenance_run_oci_database_maintenance_run["id"])
package main
import (
	"github.com/pulumi/pulumi-oci/sdk/v2/go/oci/database"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := database.GetMaintenanceRun(ctx, &database.GetMaintenanceRunArgs{
			MaintenanceRunId: testMaintenanceRunOciDatabaseMaintenanceRun.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() => 
{
    var testMaintenanceRun = Oci.Database.GetMaintenanceRun.Invoke(new()
    {
        MaintenanceRunId = testMaintenanceRunOciDatabaseMaintenanceRun.Id,
    });
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.DatabaseFunctions;
import com.pulumi.oci.Database.inputs.GetMaintenanceRunArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }
    public static void stack(Context ctx) {
        final var testMaintenanceRun = DatabaseFunctions.getMaintenanceRun(GetMaintenanceRunArgs.builder()
            .maintenanceRunId(testMaintenanceRunOciDatabaseMaintenanceRun.id())
            .build());
    }
}
variables:
  testMaintenanceRun:
    fn::invoke:
      function: oci:Database:getMaintenanceRun
      arguments:
        maintenanceRunId: ${testMaintenanceRunOciDatabaseMaintenanceRun.id}
Using getMaintenanceRun
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getMaintenanceRun(args: GetMaintenanceRunArgs, opts?: InvokeOptions): Promise<GetMaintenanceRunResult>
function getMaintenanceRunOutput(args: GetMaintenanceRunOutputArgs, opts?: InvokeOptions): Output<GetMaintenanceRunResult>def get_maintenance_run(maintenance_run_id: Optional[str] = None,
                        opts: Optional[InvokeOptions] = None) -> GetMaintenanceRunResult
def get_maintenance_run_output(maintenance_run_id: Optional[pulumi.Input[str]] = None,
                        opts: Optional[InvokeOptions] = None) -> Output[GetMaintenanceRunResult]func LookupMaintenanceRun(ctx *Context, args *LookupMaintenanceRunArgs, opts ...InvokeOption) (*LookupMaintenanceRunResult, error)
func LookupMaintenanceRunOutput(ctx *Context, args *LookupMaintenanceRunOutputArgs, opts ...InvokeOption) LookupMaintenanceRunResultOutput> Note: This function is named LookupMaintenanceRun in the Go SDK.
public static class GetMaintenanceRun 
{
    public static Task<GetMaintenanceRunResult> InvokeAsync(GetMaintenanceRunArgs args, InvokeOptions? opts = null)
    public static Output<GetMaintenanceRunResult> Invoke(GetMaintenanceRunInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetMaintenanceRunResult> getMaintenanceRun(GetMaintenanceRunArgs args, InvokeOptions options)
public static Output<GetMaintenanceRunResult> getMaintenanceRun(GetMaintenanceRunArgs args, InvokeOptions options)
fn::invoke:
  function: oci:Database/getMaintenanceRun:getMaintenanceRun
  arguments:
    # arguments dictionaryThe following arguments are supported:
- MaintenanceRun stringId 
- The maintenance run OCID.
- MaintenanceRun stringId 
- The maintenance run OCID.
- maintenanceRun StringId 
- The maintenance run OCID.
- maintenanceRun stringId 
- The maintenance run OCID.
- maintenance_run_ strid 
- The maintenance run OCID.
- maintenanceRun StringId 
- The maintenance run OCID.
getMaintenanceRun Result
The following output properties are available:
- CompartmentId string
- The OCID of the compartment.
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching List<GetTimes Maintenance Run Estimated Patching Time> 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- Id string
- The OCID of the maintenance run.
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsDst boolFile Update Enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceRun stringId 
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId string
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchType string
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance List<string>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringId 
- The ID of the target resource on which the maintenance run occurs.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeScheduled string
- The date and time the maintenance run is scheduled to occur.
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- CompartmentId string
- The OCID of the compartment.
- CurrentCustom intAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- CurrentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- CustomAction intTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- DatabaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- DisplayName string
- The user-friendly name for the maintenance run.
- EstimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- EstimatedPatching []GetTimes Maintenance Run Estimated Patching Time 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- Id string
- The OCID of the maintenance run.
- IsCustom boolAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- IsDst boolFile Update Enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- IsMaintenance boolRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceRun stringId 
- MaintenanceSubtype string
- Maintenance sub-type.
- MaintenanceType string
- Maintenance type.
- PatchFailure intCount 
- Contain the patch failure count.
- PatchId string
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- PatchType string
- PatchingEnd stringTime 
- The time when the patching operation ended.
- PatchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- PatchingStart stringTime 
- The time when the patching operation started.
- PatchingStatus string
- The status of the patching operation.
- PeerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- PeerMaintenance []stringRun Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- TargetDb stringServer Version 
- The target software version for the database server patching operation.
- TargetResource stringId 
- The ID of the target resource on which the maintenance run occurs.
- TargetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- TargetStorage stringServer Version 
- The target Cell version that is to be patched to.
- TimeEnded string
- The date and time the maintenance run was completed.
- TimeScheduled string
- The date and time the maintenance run is scheduled to occur.
- TimeStarted string
- The date and time the maintenance run starts.
- TotalTime intTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId String
- The OCID of the compartment.
- currentCustom IntegerAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction IntegerTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching List<GetTimes Maintenance Run Estimated Patching Time> 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id String
- The OCID of the maintenance run.
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst BooleanFile Update Enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceRun StringId 
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure IntegerCount 
- Contain the patch failure count.
- patchId String
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType String
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringId 
- The ID of the target resource on which the maintenance run occurs.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeScheduled String
- The date and time the maintenance run is scheduled to occur.
- timeStarted String
- The date and time the maintenance run starts.
- totalTime IntegerTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId string
- The OCID of the compartment.
- currentCustom numberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching stringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction numberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- databaseSoftware stringImage Id 
- The Autonomous Database Software Image OCID
- description string
- Description of the maintenance run.
- displayName string
- The user-friendly name for the maintenance run.
- estimatedComponent stringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching GetTimes Maintenance Run Estimated Patching Time[] 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id string
- The OCID of the maintenance run.
- isCustom booleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst booleanFile Update Enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- isMaintenance booleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- maintenanceRun stringId 
- maintenanceSubtype string
- Maintenance sub-type.
- maintenanceType string
- Maintenance type.
- patchFailure numberCount 
- Contain the patch failure count.
- patchId string
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType string
- patchingEnd stringTime 
- The time when the patching operation ended.
- patchingMode string
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patchingStart stringTime 
- The time when the patching operation started.
- patchingStatus string
- The status of the patching operation.
- peerMaintenance stringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance string[]Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb stringServer Version 
- The target software version for the database server patching operation.
- targetResource stringId 
- The ID of the target resource on which the maintenance run occurs.
- targetResource stringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage stringServer Version 
- The target Cell version that is to be patched to.
- timeEnded string
- The date and time the maintenance run was completed.
- timeScheduled string
- The date and time the maintenance run is scheduled to occur.
- timeStarted string
- The date and time the maintenance run starts.
- totalTime numberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
- compartment_id str
- The OCID of the compartment.
- current_custom_ intaction_ timeout_ in_ mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current_patching_ strcomponent 
- The name of the current infrastruture component that is getting patched.
- custom_action_ inttimeout_ in_ mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- database_software_ strimage_ id 
- The Autonomous Database Software Image OCID
- description str
- Description of the maintenance run.
- display_name str
- The user-friendly name for the maintenance run.
- estimated_component_ strpatching_ start_ time 
- The estimated start time of the next infrastruture component patching operation.
- estimated_patching_ Sequence[Gettimes Maintenance Run Estimated Patching Time] 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id str
- The OCID of the maintenance run.
- is_custom_ boolaction_ timeout_ enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is_dst_ boolfile_ update_ enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- is_maintenance_ boolrun_ granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycle_details str
- Additional information about the current lifecycle state.
- maintenance_run_ strid 
- maintenance_subtype str
- Maintenance sub-type.
- maintenance_type str
- Maintenance type.
- patch_failure_ intcount 
- Contain the patch failure count.
- patch_id str
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patch_type str
- patching_end_ strtime 
- The time when the patching operation ended.
- patching_mode str
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patching_start_ strtime 
- The time when the patching operation started.
- patching_status str
- The status of the patching operation.
- peer_maintenance_ strrun_ id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peer_maintenance_ Sequence[str]run_ ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state str
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target_db_ strserver_ version 
- The target software version for the database server patching operation.
- target_resource_ strid 
- The ID of the target resource on which the maintenance run occurs.
- target_resource_ strtype 
- The type of the target resource on which the maintenance run occurs.
- target_storage_ strserver_ version 
- The target Cell version that is to be patched to.
- time_ended str
- The date and time the maintenance run was completed.
- time_scheduled str
- The date and time the maintenance run is scheduled to occur.
- time_started str
- The date and time the maintenance run starts.
- total_time_ inttaken_ in_ mins 
- The total time taken by corresponding resource activity in minutes.
- compartmentId String
- The OCID of the compartment.
- currentCustom NumberAction Timeout In Mins 
- Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- currentPatching StringComponent 
- The name of the current infrastruture component that is getting patched.
- customAction NumberTimeout In Mins 
- Determines the amount of time the system will wait before the start of each database server patching operation. Specify a number of minutes, from 15 to 120.
- databaseSoftware StringImage Id 
- The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- displayName String
- The user-friendly name for the maintenance run.
- estimatedComponent StringPatching Start Time 
- The estimated start time of the next infrastruture component patching operation.
- estimatedPatching List<Property Map>Times 
- The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- id String
- The OCID of the maintenance run.
- isCustom BooleanAction Timeout Enabled 
- If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- isDst BooleanFile Update Enabled 
- Indicates if an automatic DST Time Zone file update is enabled for the Autonomous Container Database. If enabled along with Release Update, patching will be done in a Non-Rolling manner.
- isMaintenance BooleanRun Granular 
- If FALSE, the maintenance run doesn't support granular maintenance.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceRun StringId 
- maintenanceSubtype String
- Maintenance sub-type.
- maintenanceType String
- Maintenance type.
- patchFailure NumberCount 
- Contain the patch failure count.
- patchId String
- The unique identifier of the patch. The identifier string includes the patch type, the Oracle Database version, and the patch creation date (using the format YYMMDD). For example, the identifier ru_patch_19.9.0.0_201030is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020.
- patchType String
- patchingEnd StringTime 
- The time when the patching operation ended.
- patchingMode String
- Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- patchingStart StringTime 
- The time when the patching operation started.
- patchingStatus String
- The status of the patching operation.
- peerMaintenance StringRun Id 
- The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- peerMaintenance List<String>Run Ids 
- The list of OCIDs for the maintenance runs associated with their Autonomous Data Guard peer container databases.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- targetDb StringServer Version 
- The target software version for the database server patching operation.
- targetResource StringId 
- The ID of the target resource on which the maintenance run occurs.
- targetResource StringType 
- The type of the target resource on which the maintenance run occurs.
- targetStorage StringServer Version 
- The target Cell version that is to be patched to.
- timeEnded String
- The date and time the maintenance run was completed.
- timeScheduled String
- The date and time the maintenance run is scheduled to occur.
- timeStarted String
- The date and time the maintenance run starts.
- totalTime NumberTaken In Mins 
- The total time taken by corresponding resource activity in minutes.
Supporting Types
GetMaintenanceRunEstimatedPatchingTime     
- EstimatedDb intServer Patching Time 
- The estimated time required in minutes for database server patching.
- EstimatedNetwork intSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- EstimatedStorage intServer Patching Time 
- The estimated time required in minutes for storage server patching.
- TotalEstimated intPatching Time 
- The estimated total time required in minutes for all patching operations.
- EstimatedDb intServer Patching Time 
- The estimated time required in minutes for database server patching.
- EstimatedNetwork intSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- EstimatedStorage intServer Patching Time 
- The estimated time required in minutes for storage server patching.
- TotalEstimated intPatching Time 
- The estimated total time required in minutes for all patching operations.
- estimatedDb IntegerServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork IntegerSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage IntegerServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated IntegerPatching Time 
- The estimated total time required in minutes for all patching operations.
- estimatedDb numberServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork numberSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage numberServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated numberPatching Time 
- The estimated total time required in minutes for all patching operations.
- estimated_db_ intserver_ patching_ time 
- The estimated time required in minutes for database server patching.
- estimated_network_ intswitches_ patching_ time 
- The estimated time required in minutes for network switch patching.
- estimated_storage_ intserver_ patching_ time 
- The estimated time required in minutes for storage server patching.
- total_estimated_ intpatching_ time 
- The estimated total time required in minutes for all patching operations.
- estimatedDb NumberServer Patching Time 
- The estimated time required in minutes for database server patching.
- estimatedNetwork NumberSwitches Patching Time 
- The estimated time required in minutes for network switch patching.
- estimatedStorage NumberServer Patching Time 
- The estimated time required in minutes for storage server patching.
- totalEstimated NumberPatching Time 
- The estimated total time required in minutes for all patching operations.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the ociTerraform Provider.