oci.Database.MaintenanceRun
Explore with Pulumi AI
This resource provides the Maintenance Run resource in Oracle Cloud Infrastructure Database service.
Creates a maintenance run with one of the following: The latest available release update patch (RUP) for the Autonomous Container Database. The latest available RUP and DST time zone (TZ) file updates for the Autonomous Container Database. Creates a maintenance run to update the DST TZ file for the Autonomous Container Database.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testMaintenanceRun = new oci.database.MaintenanceRun("test_maintenance_run", {
patchType: maintenanceRunPatchType,
targetResourceId: testResource.id,
timeScheduled: maintenanceRunTimeScheduled,
compartmentId: compartmentId,
databaseSoftwareImageId: testDatabaseSoftwareImage.id,
isDstFileUpdateEnabled: maintenanceRunIsDstFileUpdateEnabled,
patchingMode: maintenanceRunPatchingMode,
});
import pulumi
import pulumi_oci as oci
test_maintenance_run = oci.database.MaintenanceRun("test_maintenance_run",
patch_type=maintenance_run_patch_type,
target_resource_id=test_resource["id"],
time_scheduled=maintenance_run_time_scheduled,
compartment_id=compartment_id,
database_software_image_id=test_database_software_image["id"],
is_dst_file_update_enabled=maintenance_run_is_dst_file_update_enabled,
patching_mode=maintenance_run_patching_mode)
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.NewMaintenanceRun(ctx, "test_maintenance_run", &Database.MaintenanceRunArgs{
PatchType: pulumi.Any(maintenanceRunPatchType),
TargetResourceId: pulumi.Any(testResource.Id),
TimeScheduled: pulumi.Any(maintenanceRunTimeScheduled),
CompartmentId: pulumi.Any(compartmentId),
DatabaseSoftwareImageId: pulumi.Any(testDatabaseSoftwareImage.Id),
IsDstFileUpdateEnabled: pulumi.Any(maintenanceRunIsDstFileUpdateEnabled),
PatchingMode: pulumi.Any(maintenanceRunPatchingMode),
})
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 = new Oci.Database.MaintenanceRun("test_maintenance_run", new()
{
PatchType = maintenanceRunPatchType,
TargetResourceId = testResource.Id,
TimeScheduled = maintenanceRunTimeScheduled,
CompartmentId = compartmentId,
DatabaseSoftwareImageId = testDatabaseSoftwareImage.Id,
IsDstFileUpdateEnabled = maintenanceRunIsDstFileUpdateEnabled,
PatchingMode = maintenanceRunPatchingMode,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.MaintenanceRun;
import com.pulumi.oci.Database.MaintenanceRunArgs;
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) {
var testMaintenanceRun = new MaintenanceRun("testMaintenanceRun", MaintenanceRunArgs.builder()
.patchType(maintenanceRunPatchType)
.targetResourceId(testResource.id())
.timeScheduled(maintenanceRunTimeScheduled)
.compartmentId(compartmentId)
.databaseSoftwareImageId(testDatabaseSoftwareImage.id())
.isDstFileUpdateEnabled(maintenanceRunIsDstFileUpdateEnabled)
.patchingMode(maintenanceRunPatchingMode)
.build());
}
}
resources:
testMaintenanceRun:
type: oci:Database:MaintenanceRun
name: test_maintenance_run
properties:
patchType: ${maintenanceRunPatchType}
targetResourceId: ${testResource.id}
timeScheduled: ${maintenanceRunTimeScheduled}
compartmentId: ${compartmentId}
databaseSoftwareImageId: ${testDatabaseSoftwareImage.id}
isDstFileUpdateEnabled: ${maintenanceRunIsDstFileUpdateEnabled}
patchingMode: ${maintenanceRunPatchingMode}
Create MaintenanceRun Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new MaintenanceRun(name: string, args: MaintenanceRunArgs, opts?: CustomResourceOptions);
@overload
def MaintenanceRun(resource_name: str,
args: MaintenanceRunArgs,
opts: Optional[ResourceOptions] = None)
@overload
def MaintenanceRun(resource_name: str,
opts: Optional[ResourceOptions] = None,
patch_type: Optional[str] = None,
target_resource_id: Optional[str] = None,
time_scheduled: Optional[str] = None,
compartment_id: Optional[str] = None,
database_software_image_id: Optional[str] = None,
is_dst_file_update_enabled: Optional[bool] = None,
patching_mode: Optional[str] = None)
func NewMaintenanceRun(ctx *Context, name string, args MaintenanceRunArgs, opts ...ResourceOption) (*MaintenanceRun, error)
public MaintenanceRun(string name, MaintenanceRunArgs args, CustomResourceOptions? opts = null)
public MaintenanceRun(String name, MaintenanceRunArgs args)
public MaintenanceRun(String name, MaintenanceRunArgs args, CustomResourceOptions options)
type: oci:Database:MaintenanceRun
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args MaintenanceRunArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var maintenanceRunResource = new Oci.Database.MaintenanceRun("maintenanceRunResource", new()
{
PatchType = "string",
TargetResourceId = "string",
TimeScheduled = "string",
CompartmentId = "string",
DatabaseSoftwareImageId = "string",
IsDstFileUpdateEnabled = false,
PatchingMode = "string",
});
example, err := Database.NewMaintenanceRun(ctx, "maintenanceRunResource", &Database.MaintenanceRunArgs{
PatchType: pulumi.String("string"),
TargetResourceId: pulumi.String("string"),
TimeScheduled: pulumi.String("string"),
CompartmentId: pulumi.String("string"),
DatabaseSoftwareImageId: pulumi.String("string"),
IsDstFileUpdateEnabled: pulumi.Bool(false),
PatchingMode: pulumi.String("string"),
})
var maintenanceRunResource = new MaintenanceRun("maintenanceRunResource", MaintenanceRunArgs.builder()
.patchType("string")
.targetResourceId("string")
.timeScheduled("string")
.compartmentId("string")
.databaseSoftwareImageId("string")
.isDstFileUpdateEnabled(false)
.patchingMode("string")
.build());
maintenance_run_resource = oci.database.MaintenanceRun("maintenanceRunResource",
patch_type="string",
target_resource_id="string",
time_scheduled="string",
compartment_id="string",
database_software_image_id="string",
is_dst_file_update_enabled=False,
patching_mode="string")
const maintenanceRunResource = new oci.database.MaintenanceRun("maintenanceRunResource", {
patchType: "string",
targetResourceId: "string",
timeScheduled: "string",
compartmentId: "string",
databaseSoftwareImageId: "string",
isDstFileUpdateEnabled: false,
patchingMode: "string",
});
type: oci:Database:MaintenanceRun
properties:
compartmentId: string
databaseSoftwareImageId: string
isDstFileUpdateEnabled: false
patchType: string
patchingMode: string
targetResourceId: string
timeScheduled: string
MaintenanceRun Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The MaintenanceRun resource accepts the following input properties:
- Patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- Target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- Time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- Database
Software stringImage Id - The Autonomous Database Software Image OCID
- 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.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- Target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- Time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- Database
Software stringImage Id - The Autonomous Database Software Image OCID
- 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.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patch
Type String - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- target
Resource StringId - The ID of the target resource for which the maintenance run should be created.
- time
Scheduled String (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - The OCID of the compartment containing the Maintenance Run.
- database
Software StringImage Id - The Autonomous Database Software Image OCID
- is
Dst 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.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- database
Software stringImage Id - The Autonomous Database Software Image OCID
- is
Dst 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.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patch_
type str - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- target_
resource_ strid - The ID of the target resource for which the maintenance run should be created.
- time_
scheduled str (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment_
id str - The OCID of the compartment containing the Maintenance Run.
- database_
software_ strimage_ id - The Autonomous Database Software Image OCID
- 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.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patch
Type String - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- target
Resource StringId - The ID of the target resource for which the maintenance run should be created.
- time
Scheduled String (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - The OCID of the compartment containing the Maintenance Run.
- database
Software StringImage Id - The Autonomous Database Software Image OCID
- is
Dst 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.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
Outputs
All input properties are implicitly available as output properties. Additionally, the MaintenanceRun resource produces the following output properties:
- 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 stringComponent - 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.
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching List<MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- Is
Custom boolAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patching
End stringTime - The time when the patching operation ended.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Started string - The date and time the maintenance run starts.
- 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 stringComponent - 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.
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching []MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- Is
Custom boolAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patching
End stringTime - The time when the patching operation ended.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Started string - The date and time the maintenance run starts.
- current
Custom IntegerAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching List<MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure IntegerCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patching
End StringTime - The time when the patching operation ended.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Started String - The date and time the maintenance run starts.
- current
Custom numberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching stringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- description string
- Description of the maintenance run.
- display
Name string - The user-friendly name for the maintenance run.
- estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching MaintenanceTimes 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 provider-assigned unique ID for this managed resource.
- is
Custom booleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- lifecycle
Details string - Additional information about the current lifecycle state.
- maintenance
Subtype string - Maintenance sub-type.
- maintenance
Type string - Maintenance type.
- patch
Failure numberCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patching
End stringTime - The time when the patching operation ended.
- patching
Start stringTime - The time when the patching operation started.
- patching
Status string - The status of the patching operation.
- peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db stringServer Version - The target software version for the database server patching operation.
- target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- target
Storage stringServer Version - The target Cell version that is to be patched to.
- time
Ended string - The date and time the maintenance run was completed.
- time
Started string - The date and time the maintenance run starts.
- 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.
- 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[database.times 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 provider-assigned unique ID for this managed resource.
- is_
custom_ boolaction_ timeout_ enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- lifecycle_
details str - Additional information about the current lifecycle state.
- 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patching_
end_ strtime - The time when the patching operation ended.
- 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.
- 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_ 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_
started str - The date and time the maintenance run starts.
- current
Custom NumberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching 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 provider-assigned unique ID for this managed resource.
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure NumberCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patching
End StringTime - The time when the patching operation ended.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Started String - The date and time the maintenance run starts.
Look up Existing MaintenanceRun Resource
Get an existing MaintenanceRun resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: MaintenanceRunState, opts?: CustomResourceOptions): MaintenanceRun
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
compartment_id: Optional[str] = None,
current_custom_action_timeout_in_mins: Optional[int] = None,
current_patching_component: Optional[str] = None,
custom_action_timeout_in_mins: Optional[int] = None,
database_software_image_id: Optional[str] = None,
description: Optional[str] = None,
display_name: Optional[str] = None,
estimated_component_patching_start_time: Optional[str] = None,
estimated_patching_times: Optional[Sequence[_database.MaintenanceRunEstimatedPatchingTimeArgs]] = None,
is_custom_action_timeout_enabled: Optional[bool] = None,
is_dst_file_update_enabled: Optional[bool] = None,
lifecycle_details: Optional[str] = None,
maintenance_subtype: Optional[str] = None,
maintenance_type: Optional[str] = None,
patch_failure_count: Optional[int] = None,
patch_id: Optional[str] = None,
patch_type: Optional[str] = None,
patching_end_time: Optional[str] = None,
patching_mode: Optional[str] = None,
patching_start_time: Optional[str] = None,
patching_status: Optional[str] = None,
peer_maintenance_run_id: Optional[str] = None,
state: Optional[str] = None,
target_db_server_version: Optional[str] = None,
target_resource_id: Optional[str] = None,
target_resource_type: Optional[str] = None,
target_storage_server_version: Optional[str] = None,
time_ended: Optional[str] = None,
time_scheduled: Optional[str] = None,
time_started: Optional[str] = None) -> MaintenanceRun
func GetMaintenanceRun(ctx *Context, name string, id IDInput, state *MaintenanceRunState, opts ...ResourceOption) (*MaintenanceRun, error)
public static MaintenanceRun Get(string name, Input<string> id, MaintenanceRunState? state, CustomResourceOptions? opts = null)
public static MaintenanceRun get(String name, Output<String> id, MaintenanceRunState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- 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 stringComponent - 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 stringImage Id - The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching List<MaintenanceTimes Run Estimated Patching Time> - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- 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.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- Patching
End stringTime - The time when the patching operation ended.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Time
Started string - The date and time the maintenance run starts.
- Compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- 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 stringComponent - 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 stringImage Id - The Autonomous Database Software Image OCID
- Description string
- Description of the maintenance run.
- Display
Name string - The user-friendly name for the maintenance run.
- Estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- Estimated
Patching []MaintenanceTimes Run Estimated Patching Time Args - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- 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.
- Lifecycle
Details string - Additional information about the current lifecycle state.
- Maintenance
Subtype string - Maintenance sub-type.
- Maintenance
Type string - Maintenance type.
- Patch
Failure intCount - Contain the patch failure count.
- Patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - Patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- Patching
End stringTime - The time when the patching operation ended.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- Patching
Start stringTime - The time when the patching operation started.
- Patching
Status string - The status of the patching operation.
- Peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- State string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- Target
Db stringServer Version - The target software version for the database server patching operation.
- Target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- Target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- Target
Storage stringServer Version - The target Cell version that is to be patched to.
- Time
Ended string - The date and time the maintenance run was completed.
- Time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Time
Started string - The date and time the maintenance run starts.
- compartment
Id String - The OCID of the compartment containing the Maintenance Run.
- current
Custom IntegerAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- database
Software StringImage Id - The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching List<MaintenanceTimes Run Estimated Patching Time> - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst 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.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure IntegerCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type String - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patching
End StringTime - The time when the patching operation ended.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringId - The ID of the target resource for which the maintenance run should be created.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Scheduled String (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- time
Started String - The date and time the maintenance run starts.
- compartment
Id string - The OCID of the compartment containing the Maintenance Run.
- current
Custom numberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching stringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- database
Software stringImage Id - The Autonomous Database Software Image OCID
- description string
- Description of the maintenance run.
- display
Name string - The user-friendly name for the maintenance run.
- estimated
Component stringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching MaintenanceTimes Run Estimated Patching Time[] - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- is
Custom booleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst 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.
- lifecycle
Details string - Additional information about the current lifecycle state.
- maintenance
Subtype string - Maintenance sub-type.
- maintenance
Type string - Maintenance type.
- patch
Failure numberCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type string - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patching
End stringTime - The time when the patching operation ended.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patching
Start stringTime - The time when the patching operation started.
- patching
Status string - The status of the patching operation.
- peer
Maintenance stringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state string
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db stringServer Version - The target software version for the database server patching operation.
- target
Resource stringId - The ID of the target resource for which the maintenance run should be created.
- target
Resource stringType - The type of the target resource on which the maintenance run occurs.
- target
Storage stringServer Version - The target Cell version that is to be patched to.
- time
Ended string - The date and time the maintenance run was completed.
- time
Scheduled string (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- time
Started string - The date and time the maintenance run starts.
- compartment_
id str - The OCID of the compartment containing the Maintenance Run.
- 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[database.times Maintenance Run Estimated Patching Time Args] - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- 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.
- lifecycle_
details str - Additional information about the current lifecycle state.
- 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch_
type str - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patching_
end_ strtime - The time when the patching operation ended.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- 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.
- 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 for which the maintenance run should be created.
- 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 (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- time_
started str - The date and time the maintenance run starts.
- compartment
Id String - The OCID of the compartment containing the Maintenance Run.
- current
Custom NumberAction Timeout In Mins - Extend current custom action timeout between the current database servers during waiting state, from 0 (zero) to 30 minutes.
- current
Patching StringComponent - The name of the current infrastruture component that is getting patched.
- custom
Action 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.
- database
Software StringImage Id - The Autonomous Database Software Image OCID
- description String
- Description of the maintenance run.
- display
Name String - The user-friendly name for the maintenance run.
- estimated
Component StringPatching Start Time - The estimated start time of the next infrastruture component patching operation.
- estimated
Patching List<Property Map>Times - The estimated total time required in minutes for all patching operations (database server, storage server, and network switch patching).
- is
Custom BooleanAction Timeout Enabled - If true, enables the configuration of a custom action timeout (waiting period) between database servers patching operations.
- is
Dst 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.
- lifecycle
Details String - Additional information about the current lifecycle state.
- maintenance
Subtype String - Maintenance sub-type.
- maintenance
Type String - Maintenance type.
- patch
Failure NumberCount - Contain the patch failure count.
- patch
Id 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_201030
is used for an RU patch for Oracle Database 19.9.0.0 that was released October 30, 2020. - patch
Type String - Patch type, either "QUARTERLY", "TIMEZONE" or "CUSTOM_DATABASE_SOFTWARE_IMAGE".
- patching
End StringTime - The time when the patching operation ended.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
IMPORTANT: Non-rolling infrastructure patching involves system down time. See Oracle-Managed Infrastructure Maintenance Updates for more information.
- patching
Start StringTime - The time when the patching operation started.
- patching
Status String - The status of the patching operation.
- peer
Maintenance StringRun Id - The OCID of the maintenance run for the Autonomous Data Guard association's peer container database.
- state String
- The current state of the maintenance run. For Autonomous Database Serverless instances, valid states are IN_PROGRESS, SUCCEEDED, and FAILED.
- target
Db StringServer Version - The target software version for the database server patching operation.
- target
Resource StringId - The ID of the target resource for which the maintenance run should be created.
- target
Resource StringType - The type of the target resource on which the maintenance run occurs.
- target
Storage StringServer Version - The target Cell version that is to be patched to.
- time
Ended String - The date and time the maintenance run was completed.
- time
Scheduled String (Updatable) The date and time that update should be scheduled.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- time
Started String - The date and time the maintenance run starts.
Supporting Types
MaintenanceRunEstimatedPatchingTime, MaintenanceRunEstimatedPatchingTimeArgs
- 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.
- 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.
- estimated
Db IntegerServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network IntegerSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage IntegerServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated IntegerPatching Time - The estimated total time required in minutes for all patching operations.
- estimated
Db numberServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network numberSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage numberServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated 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.
- estimated
Db NumberServer Patching Time - The estimated time required in minutes for database server patching.
- estimated
Network NumberSwitches Patching Time - The estimated time required in minutes for network switch patching.
- estimated
Storage NumberServer Patching Time - The estimated time required in minutes for storage server patching.
- total
Estimated NumberPatching Time - The estimated total time required in minutes for all patching operations.
Import
MaintenanceRuns can be imported using the id
, e.g.
$ pulumi import oci:Database/maintenanceRun:MaintenanceRun test_maintenance_run "id"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.