oci.Database.getAutonomousVmCluster
Explore with Pulumi AI
This data source provides details about a specific Autonomous Vm Cluster resource in Oracle Cloud Infrastructure Database service.
Gets information about the specified Autonomous VM cluster for an Exadata Cloud@Customer system. To get information about an Autonomous VM Cluster in the Oracle cloud, see GetCloudAutonomousVmCluster.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testAutonomousVmCluster = oci.Database.getAutonomousVmCluster({
    autonomousVmClusterId: testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id,
});
import pulumi
import pulumi_oci as oci
test_autonomous_vm_cluster = oci.Database.get_autonomous_vm_cluster(autonomous_vm_cluster_id=test_autonomous_vm_cluster_oci_database_autonomous_vm_cluster["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.GetAutonomousVmCluster(ctx, &database.GetAutonomousVmClusterArgs{
			AutonomousVmClusterId: testAutonomousVmClusterOciDatabaseAutonomousVmCluster.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 testAutonomousVmCluster = Oci.Database.GetAutonomousVmCluster.Invoke(new()
    {
        AutonomousVmClusterId = testAutonomousVmClusterOciDatabaseAutonomousVmCluster.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.GetAutonomousVmClusterArgs;
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 testAutonomousVmCluster = DatabaseFunctions.getAutonomousVmCluster(GetAutonomousVmClusterArgs.builder()
            .autonomousVmClusterId(testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id())
            .build());
    }
}
variables:
  testAutonomousVmCluster:
    fn::invoke:
      function: oci:Database:getAutonomousVmCluster
      arguments:
        autonomousVmClusterId: ${testAutonomousVmClusterOciDatabaseAutonomousVmCluster.id}
Using getAutonomousVmCluster
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 getAutonomousVmCluster(args: GetAutonomousVmClusterArgs, opts?: InvokeOptions): Promise<GetAutonomousVmClusterResult>
function getAutonomousVmClusterOutput(args: GetAutonomousVmClusterOutputArgs, opts?: InvokeOptions): Output<GetAutonomousVmClusterResult>def get_autonomous_vm_cluster(autonomous_vm_cluster_id: Optional[str] = None,
                              opts: Optional[InvokeOptions] = None) -> GetAutonomousVmClusterResult
def get_autonomous_vm_cluster_output(autonomous_vm_cluster_id: Optional[pulumi.Input[str]] = None,
                              opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousVmClusterResult]func LookupAutonomousVmCluster(ctx *Context, args *LookupAutonomousVmClusterArgs, opts ...InvokeOption) (*LookupAutonomousVmClusterResult, error)
func LookupAutonomousVmClusterOutput(ctx *Context, args *LookupAutonomousVmClusterOutputArgs, opts ...InvokeOption) LookupAutonomousVmClusterResultOutput> Note: This function is named LookupAutonomousVmCluster in the Go SDK.
public static class GetAutonomousVmCluster 
{
    public static Task<GetAutonomousVmClusterResult> InvokeAsync(GetAutonomousVmClusterArgs args, InvokeOptions? opts = null)
    public static Output<GetAutonomousVmClusterResult> Invoke(GetAutonomousVmClusterInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetAutonomousVmClusterResult> getAutonomousVmCluster(GetAutonomousVmClusterArgs args, InvokeOptions options)
public static Output<GetAutonomousVmClusterResult> getAutonomousVmCluster(GetAutonomousVmClusterArgs args, InvokeOptions options)
fn::invoke:
  function: oci:Database/getAutonomousVmCluster:getAutonomousVmCluster
  arguments:
    # arguments dictionaryThe following arguments are supported:
- AutonomousVm stringCluster Id 
- The autonomous VM cluster OCID.
- AutonomousVm stringCluster Id 
- The autonomous VM cluster OCID.
- autonomousVm StringCluster Id 
- The autonomous VM cluster OCID.
- autonomousVm stringCluster Id 
- The autonomous VM cluster OCID.
- autonomous_vm_ strcluster_ id 
- The autonomous VM cluster OCID.
- autonomousVm StringCluster Id 
- The autonomous VM cluster OCID.
getAutonomousVmCluster Result
The following output properties are available:
- AutonomousData doubleStorage Percentage 
- AutonomousData doubleStorage Size In Tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- AutonomousVm stringCluster Id 
- AvailableAutonomous doubleData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- AvailableContainer intDatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- AvailableCpus int
- The numnber of CPU cores available.
- AvailableData doubleStorage Size In Tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel string
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- CpuCore intCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- CpuPercentage double
- CpusEnabled int
- The number of enabled CPU cores.
- CpusLowest intScaled Value 
- The lowest value to which cpus can be scaled down.
- DataStorage doubleSize In Gb 
- The total data storage allocated in GBs.
- DataStorage doubleSize In Tbs 
- The total data storage allocated in TBs
- DbNode intStorage Size In Gbs 
- The local node storage allocated in GBs.
- DbServers List<string>
- The list of OCIDs of the Db servers.
- Dictionary<string, string>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- DisplayName string
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- ExadataInfrastructure stringId 
- The OCID of the Exadata infrastructure.
- ExadataStorage doubleIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- Dictionary<string, string>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- Id string
- The OCID of the Autonomous VM cluster.
- IsLocal boolBackup Enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- IsMtls boolEnabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LicenseModel string
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceWindow List<GetDetails Autonomous Vm Cluster Maintenance Window Detail> 
- MaintenanceWindows List<GetAutonomous Vm Cluster Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MaxAcds intLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- MemorySize intIn Gbs 
- The memory allocated in GBs.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NodeCount int
- The number of nodes in the Autonomous VM Cluster.
- NonProvisionable intAutonomous Container Databases 
- OcpusEnabled double
- The number of enabled OCPU cores.
- ProvisionableAutonomous intContainer Databases 
- Deprecated. Use field totalContainerDatabases.
- ProvisionedAutonomous intContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedCpus double
- The number of CPUs provisioned in an Autonomous VM Cluster.
- ReclaimableCpus int
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- ReservedCpus double
- The number of CPUs reserved in an Autonomous VM Cluster.
- ScanListener intPort Non Tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- ScanListener intPort Tls 
- The SCAN Listener TLS port number. Default value is 2484.
- State string
- The current state of the Autonomous VM cluster.
- TimeCreated string
- The date and time that the Autonomous VM cluster was created.
- TimeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- TimeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- TimeZone string
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- TotalAutonomous doubleData Storage In Tbs 
- TotalContainer intDatabases 
- The total number of Autonomous Container Databases that can be created.
- VmCluster stringNetwork Id 
- The OCID of the VM cluster network.
- AutonomousData float64Storage Percentage 
- AutonomousData float64Storage Size In Tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- AutonomousVm stringCluster Id 
- AvailableAutonomous float64Data Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- AvailableContainer intDatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- AvailableCpus int
- The numnber of CPU cores available.
- AvailableData float64Storage Size In Tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- CompartmentId string
- The OCID of the compartment.
- ComputeModel string
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- CpuCore intCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- CpuPercentage float64
- CpusEnabled int
- The number of enabled CPU cores.
- CpusLowest intScaled Value 
- The lowest value to which cpus can be scaled down.
- DataStorage float64Size In Gb 
- The total data storage allocated in GBs.
- DataStorage float64Size In Tbs 
- The total data storage allocated in TBs
- DbNode intStorage Size In Gbs 
- The local node storage allocated in GBs.
- DbServers []string
- The list of OCIDs of the Db servers.
- map[string]string
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- DisplayName string
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- ExadataInfrastructure stringId 
- The OCID of the Exadata infrastructure.
- ExadataStorage float64In Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- map[string]string
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- Id string
- The OCID of the Autonomous VM cluster.
- IsLocal boolBackup Enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- IsMtls boolEnabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- LastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- LicenseModel string
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- LifecycleDetails string
- Additional information about the current lifecycle state.
- MaintenanceWindow []GetDetails Autonomous Vm Cluster Maintenance Window Detail 
- MaintenanceWindows []GetAutonomous Vm Cluster Maintenance Window 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- MaxAcds intLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- MemoryPer intOracle Compute Unit In Gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- MemorySize intIn Gbs 
- The memory allocated in GBs.
- NextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- NodeCount int
- The number of nodes in the Autonomous VM Cluster.
- NonProvisionable intAutonomous Container Databases 
- OcpusEnabled float64
- The number of enabled OCPU cores.
- ProvisionableAutonomous intContainer Databases 
- Deprecated. Use field totalContainerDatabases.
- ProvisionedAutonomous intContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- ProvisionedCpus float64
- The number of CPUs provisioned in an Autonomous VM Cluster.
- ReclaimableCpus int
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- ReservedCpus float64
- The number of CPUs reserved in an Autonomous VM Cluster.
- ScanListener intPort Non Tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- ScanListener intPort Tls 
- The SCAN Listener TLS port number. Default value is 2484.
- State string
- The current state of the Autonomous VM cluster.
- TimeCreated string
- The date and time that the Autonomous VM cluster was created.
- TimeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- TimeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- TimeZone string
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- TotalAutonomous float64Data Storage In Tbs 
- TotalContainer intDatabases 
- The total number of Autonomous Container Databases that can be created.
- VmCluster stringNetwork Id 
- The OCID of the VM cluster network.
- autonomousData DoubleStorage Percentage 
- autonomousData DoubleStorage Size In Tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- autonomousVm StringCluster Id 
- availableAutonomous DoubleData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer IntegerDatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- availableCpus Integer
- The numnber of CPU cores available.
- availableData DoubleStorage Size In Tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- compartmentId String
- The OCID of the compartment.
- computeModel String
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore IntegerCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage Double
- cpusEnabled Integer
- The number of enabled CPU cores.
- cpusLowest IntegerScaled Value 
- The lowest value to which cpus can be scaled down.
- dataStorage DoubleSize In Gb 
- The total data storage allocated in GBs.
- dataStorage DoubleSize In Tbs 
- The total data storage allocated in TBs
- dbNode IntegerStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers List<String>
- The list of OCIDs of the Db servers.
- Map<String,String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName String
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadataInfrastructure StringId 
- The OCID of the Exadata infrastructure.
- exadataStorage DoubleIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- Map<String,String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- id String
- The OCID of the Autonomous VM cluster.
- isLocal BooleanBackup Enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- isMtls BooleanEnabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- licenseModel String
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceWindow List<GetDetails Autonomous Vm Cluster Maintenance Window Detail> 
- maintenanceWindows List<GetAutonomous Vm Cluster Maintenance Window> 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds IntegerLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer IntegerOracle Compute Unit In Gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- memorySize IntegerIn Gbs 
- The memory allocated in GBs.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nodeCount Integer
- The number of nodes in the Autonomous VM Cluster.
- nonProvisionable IntegerAutonomous Container Databases 
- ocpusEnabled Double
- The number of enabled OCPU cores.
- provisionableAutonomous IntegerContainer Databases 
- Deprecated. Use field totalContainerDatabases.
- provisionedAutonomous IntegerContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus Double
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus Integer
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus Double
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener IntegerPort Non Tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- scanListener IntegerPort Tls 
- The SCAN Listener TLS port number. Default value is 2484.
- state String
- The current state of the Autonomous VM cluster.
- timeCreated String
- The date and time that the Autonomous VM cluster was created.
- timeDatabase StringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds StringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeZone String
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- totalAutonomous DoubleData Storage In Tbs 
- totalContainer IntegerDatabases 
- The total number of Autonomous Container Databases that can be created.
- vmCluster StringNetwork Id 
- The OCID of the VM cluster network.
- autonomousData numberStorage Percentage 
- autonomousData numberStorage Size In Tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- autonomousVm stringCluster Id 
- availableAutonomous numberData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer numberDatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- availableCpus number
- The numnber of CPU cores available.
- availableData numberStorage Size In Tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- compartmentId string
- The OCID of the compartment.
- computeModel string
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore numberCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage number
- cpusEnabled number
- The number of enabled CPU cores.
- cpusLowest numberScaled Value 
- The lowest value to which cpus can be scaled down.
- dataStorage numberSize In Gb 
- The total data storage allocated in GBs.
- dataStorage numberSize In Tbs 
- The total data storage allocated in TBs
- dbNode numberStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers string[]
- The list of OCIDs of the Db servers.
- {[key: string]: string}
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName string
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadataInfrastructure stringId 
- The OCID of the Exadata infrastructure.
- exadataStorage numberIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- {[key: string]: string}
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- id string
- The OCID of the Autonomous VM cluster.
- isLocal booleanBackup Enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- isMtls booleanEnabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- lastMaintenance stringRun Id 
- The OCID of the last maintenance run.
- licenseModel string
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycleDetails string
- Additional information about the current lifecycle state.
- maintenanceWindow GetDetails Autonomous Vm Cluster Maintenance Window Detail[] 
- maintenanceWindows GetAutonomous Vm Cluster Maintenance Window[] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds numberLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer numberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- memorySize numberIn Gbs 
- The memory allocated in GBs.
- nextMaintenance stringRun Id 
- The OCID of the next maintenance run.
- nodeCount number
- The number of nodes in the Autonomous VM Cluster.
- nonProvisionable numberAutonomous Container Databases 
- ocpusEnabled number
- The number of enabled OCPU cores.
- provisionableAutonomous numberContainer Databases 
- Deprecated. Use field totalContainerDatabases.
- provisionedAutonomous numberContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus number
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus number
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus number
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener numberPort Non Tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- scanListener numberPort Tls 
- The SCAN Listener TLS port number. Default value is 2484.
- state string
- The current state of the Autonomous VM cluster.
- timeCreated string
- The date and time that the Autonomous VM cluster was created.
- timeDatabase stringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds stringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeZone string
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- totalAutonomous numberData Storage In Tbs 
- totalContainer numberDatabases 
- The total number of Autonomous Container Databases that can be created.
- vmCluster stringNetwork Id 
- The OCID of the VM cluster network.
- autonomous_data_ floatstorage_ percentage 
- autonomous_data_ floatstorage_ size_ in_ tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- autonomous_vm_ strcluster_ id 
- available_autonomous_ floatdata_ storage_ size_ in_ tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- available_container_ intdatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- available_cpus int
- The numnber of CPU cores available.
- available_data_ floatstorage_ size_ in_ tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- compartment_id str
- The OCID of the compartment.
- compute_model str
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpu_core_ intcount_ per_ node 
- The number of CPU cores enabled per VM cluster node.
- cpu_percentage float
- cpus_enabled int
- The number of enabled CPU cores.
- cpus_lowest_ intscaled_ value 
- The lowest value to which cpus can be scaled down.
- data_storage_ floatsize_ in_ gb 
- The total data storage allocated in GBs.
- data_storage_ floatsize_ in_ tbs 
- The total data storage allocated in TBs
- db_node_ intstorage_ size_ in_ gbs 
- The local node storage allocated in GBs.
- db_servers Sequence[str]
- The list of OCIDs of the Db servers.
- Mapping[str, str]
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- display_name str
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadata_infrastructure_ strid 
- The OCID of the Exadata infrastructure.
- exadata_storage_ floatin_ tbs_ lowest_ scaled_ value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- Mapping[str, str]
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- id str
- The OCID of the Autonomous VM cluster.
- is_local_ boolbackup_ enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- is_mtls_ boolenabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- last_maintenance_ strrun_ id 
- The OCID of the last maintenance run.
- license_model str
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycle_details str
- Additional information about the current lifecycle state.
- maintenance_window_ Sequence[Getdetails Autonomous Vm Cluster Maintenance Window Detail] 
- maintenance_windows Sequence[GetAutonomous Vm Cluster Maintenance Window] 
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- max_acds_ intlowest_ scaled_ value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memory_per_ intoracle_ compute_ unit_ in_ gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- memory_size_ intin_ gbs 
- The memory allocated in GBs.
- next_maintenance_ strrun_ id 
- The OCID of the next maintenance run.
- node_count int
- The number of nodes in the Autonomous VM Cluster.
- non_provisionable_ intautonomous_ container_ databases 
- ocpus_enabled float
- The number of enabled OCPU cores.
- provisionable_autonomous_ intcontainer_ databases 
- Deprecated. Use field totalContainerDatabases.
- provisioned_autonomous_ intcontainer_ databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisioned_cpus float
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimable_cpus int
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reserved_cpus float
- The number of CPUs reserved in an Autonomous VM Cluster.
- scan_listener_ intport_ non_ tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- scan_listener_ intport_ tls 
- The SCAN Listener TLS port number. Default value is 2484.
- state str
- The current state of the Autonomous VM cluster.
- time_created str
- The date and time that the Autonomous VM cluster was created.
- time_database_ strssl_ certificate_ expires 
- The date and time of Database SSL certificate expiration.
- time_ords_ strcertificate_ expires 
- The date and time of ORDS certificate expiration.
- time_zone str
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- total_autonomous_ floatdata_ storage_ in_ tbs 
- total_container_ intdatabases 
- The total number of Autonomous Container Databases that can be created.
- vm_cluster_ strnetwork_ id 
- The OCID of the VM cluster network.
- autonomousData NumberStorage Percentage 
- autonomousData NumberStorage Size In Tbs 
- The data disk group size allocated for Autonomous Databases, in TBs.
- autonomousVm StringCluster Id 
- availableAutonomous NumberData Storage Size In Tbs 
- The data disk group size available for Autonomous Databases, in TBs.
- availableContainer NumberDatabases 
- The number of Autonomous Container Databases that can be created with the currently available local storage.
- availableCpus Number
- The numnber of CPU cores available.
- availableData NumberStorage Size In Tbs 
- Deprecated. Use availableAutonomousDataStorageSizeInTBsfor Autonomous Databases' data storage availability in TBs.
- compartmentId String
- The OCID of the compartment.
- computeModel String
- The compute model of the Autonomous VM Cluster. ECPU compute model is the recommended model and OCPU compute model is legacy. See Compute Models in Autonomous Database on Dedicated Exadata #Infrastructure for more details.
- cpuCore NumberCount Per Node 
- The number of CPU cores enabled per VM cluster node.
- cpuPercentage Number
- cpusEnabled Number
- The number of enabled CPU cores.
- cpusLowest NumberScaled Value 
- The lowest value to which cpus can be scaled down.
- dataStorage NumberSize In Gb 
- The total data storage allocated in GBs.
- dataStorage NumberSize In Tbs 
- The total data storage allocated in TBs
- dbNode NumberStorage Size In Gbs 
- The local node storage allocated in GBs.
- dbServers List<String>
- The list of OCIDs of the Db servers.
- Map<String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- displayName String
- The user-friendly name for the Autonomous VM cluster. The name does not need to be unique.
- exadataInfrastructure StringId 
- The OCID of the Exadata infrastructure.
- exadataStorage NumberIn Tbs Lowest Scaled Value 
- The lowest value to which exadataStorage(in TBs) can be scaled down.
- Map<String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {"Department": "Finance"}
- id String
- The OCID of the Autonomous VM cluster.
- isLocal BooleanBackup Enabled 
- If true, database backup on local Exadata storage is configured for the Autonomous VM cluster. If false, database backup on local Exadata storage is not available in the Autonomous VM cluster.
- isMtls BooleanEnabled 
- Enable mutual TLS(mTLS) authentication for database while provisioning a VMCluster. Default is TLS.
- lastMaintenance StringRun Id 
- The OCID of the last maintenance run.
- licenseModel String
- The Oracle license model that applies to the Autonomous VM cluster. The default is LICENSE_INCLUDED.
- lifecycleDetails String
- Additional information about the current lifecycle state.
- maintenanceWindow List<Property Map>Details 
- maintenanceWindows List<Property Map>
- The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maxAcds NumberLowest Scaled Value 
- The lowest value to which maximum number of ACDs can be scaled down.
- memoryPer NumberOracle Compute Unit In Gbs 
- The amount of memory (in GBs) to be enabled per OCPU or ECPU.
- memorySize NumberIn Gbs 
- The memory allocated in GBs.
- nextMaintenance StringRun Id 
- The OCID of the next maintenance run.
- nodeCount Number
- The number of nodes in the Autonomous VM Cluster.
- nonProvisionable NumberAutonomous Container Databases 
- ocpusEnabled Number
- The number of enabled OCPU cores.
- provisionableAutonomous NumberContainer Databases 
- Deprecated. Use field totalContainerDatabases.
- provisionedAutonomous NumberContainer Databases 
- The number of provisioned Autonomous Container Databases in an Autonomous VM Cluster.
- provisionedCpus Number
- The number of CPUs provisioned in an Autonomous VM Cluster.
- reclaimableCpus Number
- For Autonomous Databases on Dedicated Exadata Infrastructure:- These are the CPUs that continue to be included in the count of CPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available CPUs at its parent Autonomous VM Cluster level by restarting the Autonomous Container Database.
- The CPU type (OCPUs or ECPUs) is determined by the parent Autonomous Exadata VM Cluster's compute model.
 
- reservedCpus Number
- The number of CPUs reserved in an Autonomous VM Cluster.
- scanListener NumberPort Non Tls 
- The SCAN Listener Non TLS port number. Default value is 1521.
- scanListener NumberPort Tls 
- The SCAN Listener TLS port number. Default value is 2484.
- state String
- The current state of the Autonomous VM cluster.
- timeCreated String
- The date and time that the Autonomous VM cluster was created.
- timeDatabase StringSsl Certificate Expires 
- The date and time of Database SSL certificate expiration.
- timeOrds StringCertificate Expires 
- The date and time of ORDS certificate expiration.
- timeZone String
- The time zone to use for the Autonomous VM cluster. For details, see DB System Time Zones.
- totalAutonomous NumberData Storage In Tbs 
- totalContainer NumberDatabases 
- The total number of Autonomous Container Databases that can be created.
- vmCluster StringNetwork Id 
- The OCID of the VM cluster network.
Supporting Types
GetAutonomousVmClusterMaintenanceWindow     
- CustomAction intTimeout In Mins 
- DaysOf List<GetWeeks Autonomous Vm Cluster Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- IsMonthly boolPatching Enabled 
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<GetAutonomous Vm Cluster Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Preference string
- The maintenance window scheduling preference.
- SkipRus List<bool>
- WeeksOf List<int>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- CustomAction intTimeout In Mins 
- DaysOf []GetWeeks Autonomous Vm Cluster Maintenance Window Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- IsMonthly boolPatching Enabled 
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]GetAutonomous Vm Cluster Maintenance Window Month 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Preference string
- The maintenance window scheduling preference.
- SkipRus []bool
- WeeksOf []intMonths 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction IntegerTimeout In Mins 
- daysOf List<GetWeeks Autonomous Vm Cluster Maintenance Window Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- isMonthly BooleanPatching Enabled 
- leadTime IntegerIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<GetAutonomous Vm Cluster Maintenance Window Month> 
- Months during the year when maintenance should be performed.
- patchingMode String
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Integer>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction numberTimeout In Mins 
- daysOf GetWeeks Autonomous Vm Cluster Maintenance Window Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom booleanAction Timeout Enabled 
- isMonthly booleanPatching Enabled 
- leadTime numberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
GetAutonomous Vm Cluster Maintenance Window Month[] 
- Months during the year when maintenance should be performed.
- patchingMode string
- preference string
- The maintenance window scheduling preference.
- skipRus boolean[]
- weeksOf number[]Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_action_ inttimeout_ in_ mins 
- days_of_ Sequence[Getweeks Autonomous Vm Cluster Maintenance Window Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- is_custom_ boolaction_ timeout_ enabled 
- is_monthly_ boolpatching_ enabled 
- lead_time_ intin_ weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Sequence[GetAutonomous Vm Cluster Maintenance Window Month] 
- Months during the year when maintenance should be performed.
- patching_mode str
- preference str
- The maintenance window scheduling preference.
- skip_rus Sequence[bool]
- weeks_of_ Sequence[int]months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction NumberTimeout In Mins 
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- isMonthly BooleanPatching Enabled 
- leadTime NumberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
- Months during the year when maintenance should be performed.
- patchingMode String
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Number>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousVmClusterMaintenanceWindowDaysOfWeek        
- Name string
- Name of the month of the year.
- Name string
- Name of the month of the year.
- name String
- Name of the month of the year.
- name string
- Name of the month of the year.
- name str
- Name of the month of the year.
- name String
- Name of the month of the year.
GetAutonomousVmClusterMaintenanceWindowDetail      
- CustomAction intTimeout In Mins 
- DaysOf List<GetWeeks Autonomous Vm Cluster Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- HoursOf List<int>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- IsMonthly boolPatching Enabled 
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<GetAutonomous Vm Cluster Maintenance Window Detail Month> 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Preference string
- The maintenance window scheduling preference.
- SkipRus List<bool>
- WeeksOf List<int>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- CustomAction intTimeout In Mins 
- DaysOf []GetWeeks Autonomous Vm Cluster Maintenance Window Detail Days Of Week 
- Days during the week when maintenance should be performed.
- HoursOf []intDays 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- IsCustom boolAction Timeout Enabled 
- IsMonthly boolPatching Enabled 
- LeadTime intIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]GetAutonomous Vm Cluster Maintenance Window Detail Month 
- Months during the year when maintenance should be performed.
- PatchingMode string
- Preference string
- The maintenance window scheduling preference.
- SkipRus []bool
- WeeksOf []intMonths 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction IntegerTimeout In Mins 
- daysOf List<GetWeeks Autonomous Vm Cluster Maintenance Window Detail Days Of Week> 
- Days during the week when maintenance should be performed.
- hoursOf List<Integer>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- isMonthly BooleanPatching Enabled 
- leadTime IntegerIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<GetAutonomous Vm Cluster Maintenance Window Detail Month> 
- Months during the year when maintenance should be performed.
- patchingMode String
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Integer>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction numberTimeout In Mins 
- daysOf GetWeeks Autonomous Vm Cluster Maintenance Window Detail Days Of Week[] 
- Days during the week when maintenance should be performed.
- hoursOf number[]Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom booleanAction Timeout Enabled 
- isMonthly booleanPatching Enabled 
- leadTime numberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
GetAutonomous Vm Cluster Maintenance Window Detail Month[] 
- Months during the year when maintenance should be performed.
- patchingMode string
- preference string
- The maintenance window scheduling preference.
- skipRus boolean[]
- weeksOf number[]Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_action_ inttimeout_ in_ mins 
- days_of_ Sequence[Getweeks Autonomous Vm Cluster Maintenance Window Detail Days Of Week] 
- Days during the week when maintenance should be performed.
- hours_of_ Sequence[int]days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- is_custom_ boolaction_ timeout_ enabled 
- is_monthly_ boolpatching_ enabled 
- lead_time_ intin_ weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Sequence[GetAutonomous Vm Cluster Maintenance Window Detail Month] 
- Months during the year when maintenance should be performed.
- patching_mode str
- preference str
- The maintenance window scheduling preference.
- skip_rus Sequence[bool]
- weeks_of_ Sequence[int]months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- customAction NumberTimeout In Mins 
- daysOf List<Property Map>Weeks 
- Days during the week when maintenance should be performed.
- hoursOf List<Number>Days 
- The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
 
- isCustom BooleanAction Timeout Enabled 
- isMonthly BooleanPatching Enabled 
- leadTime NumberIn Weeks 
- Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
- Months during the year when maintenance should be performed.
- patchingMode String
- preference String
- The maintenance window scheduling preference.
- skipRus List<Boolean>
- weeksOf List<Number>Months 
- Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
GetAutonomousVmClusterMaintenanceWindowDetailDaysOfWeek         
- Name string
- Name of the month of the year.
- Name string
- Name of the month of the year.
- name String
- Name of the month of the year.
- name string
- Name of the month of the year.
- name str
- Name of the month of the year.
- name String
- Name of the month of the year.
GetAutonomousVmClusterMaintenanceWindowDetailMonth       
- Name string
- Name of the month of the year.
- Name string
- Name of the month of the year.
- name String
- Name of the month of the year.
- name string
- Name of the month of the year.
- name str
- Name of the month of the year.
- name String
- Name of the month of the year.
GetAutonomousVmClusterMaintenanceWindowMonth      
- Name string
- Name of the month of the year.
- Name string
- Name of the month of the year.
- name String
- Name of the month of the year.
- name string
- Name of the month of the year.
- name str
- Name of the month of the year.
- name String
- Name of the month of the year.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the ociTerraform Provider.