Oracle Cloud Infrastructure v3.10.0 published on Wednesday, Nov 5, 2025 by Pulumi
oci.Ocvp.getDatastoreCluster
Start a Neo task
Explain and create an oci.Ocvp.getDatastoreCluster resource
This data source provides details about a specific Datastore Cluster resource in Oracle Cloud Infrastructure Oracle Cloud VMware Solution service.
Get the specified Datastore Cluster information.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testDatastoreCluster = oci.Ocvp.getDatastoreCluster({
datastoreClusterId: testDatastoreClusterOciOcvpDatastoreCluster.id,
});
import pulumi
import pulumi_oci as oci
test_datastore_cluster = oci.Ocvp.get_datastore_cluster(datastore_cluster_id=test_datastore_cluster_oci_ocvp_datastore_cluster["id"])
package main
import (
"github.com/pulumi/pulumi-oci/sdk/v3/go/oci/ocvp"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := ocvp.GetDatastoreCluster(ctx, &ocvp.GetDatastoreClusterArgs{
DatastoreClusterId: testDatastoreClusterOciOcvpDatastoreCluster.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 testDatastoreCluster = Oci.Ocvp.GetDatastoreCluster.Invoke(new()
{
DatastoreClusterId = testDatastoreClusterOciOcvpDatastoreCluster.Id,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Ocvp.OcvpFunctions;
import com.pulumi.oci.Ocvp.inputs.GetDatastoreClusterArgs;
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 testDatastoreCluster = OcvpFunctions.getDatastoreCluster(GetDatastoreClusterArgs.builder()
.datastoreClusterId(testDatastoreClusterOciOcvpDatastoreCluster.id())
.build());
}
}
variables:
testDatastoreCluster:
fn::invoke:
function: oci:Ocvp:getDatastoreCluster
arguments:
datastoreClusterId: ${testDatastoreClusterOciOcvpDatastoreCluster.id}
Using getDatastoreCluster
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 getDatastoreCluster(args: GetDatastoreClusterArgs, opts?: InvokeOptions): Promise<GetDatastoreClusterResult>
function getDatastoreClusterOutput(args: GetDatastoreClusterOutputArgs, opts?: InvokeOptions): Output<GetDatastoreClusterResult>def get_datastore_cluster(datastore_cluster_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetDatastoreClusterResult
def get_datastore_cluster_output(datastore_cluster_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetDatastoreClusterResult]func LookupDatastoreCluster(ctx *Context, args *LookupDatastoreClusterArgs, opts ...InvokeOption) (*LookupDatastoreClusterResult, error)
func LookupDatastoreClusterOutput(ctx *Context, args *LookupDatastoreClusterOutputArgs, opts ...InvokeOption) LookupDatastoreClusterResultOutput> Note: This function is named LookupDatastoreCluster in the Go SDK.
public static class GetDatastoreCluster
{
public static Task<GetDatastoreClusterResult> InvokeAsync(GetDatastoreClusterArgs args, InvokeOptions? opts = null)
public static Output<GetDatastoreClusterResult> Invoke(GetDatastoreClusterInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetDatastoreClusterResult> getDatastoreCluster(GetDatastoreClusterArgs args, InvokeOptions options)
public static Output<GetDatastoreClusterResult> getDatastoreCluster(GetDatastoreClusterArgs args, InvokeOptions options)
fn::invoke:
function: oci:Ocvp/getDatastoreCluster:getDatastoreCluster
arguments:
# arguments dictionaryThe following arguments are supported:
- Datastore
Cluster stringId - The OCID of the Datastore Cluster.
- Datastore
Cluster stringId - The OCID of the Datastore Cluster.
- datastore
Cluster StringId - The OCID of the Datastore Cluster.
- datastore
Cluster stringId - The OCID of the Datastore Cluster.
- datastore_
cluster_ strid - The OCID of the Datastore Cluster.
- datastore
Cluster StringId - The OCID of the Datastore Cluster.
getDatastoreCluster Result
The following output properties are available:
- Availability
Domain string - The availability domain of the Datastore Cluster.
- Capacity
In doubleGbs - Total size of all datastores associated with the datastore cluster in GB.
- Cluster
Id string - The OCID of the VMware Cluster that Datastore cluster is attached to.
- Compartment
Id string - The OCID of the compartment that contains the Datastore.
- Datastore
Cluster stringId - Datastore
Cluster stringType - Type of the datastore cluster.
- Datastore
Ids List<string> - The OCIDs of the Datastores that belong to the Datastore Cluster
- Dictionary<string, string>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - Display
Name string - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- Esxi
Host List<string>Ids - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- 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 Datastore cluster.
- Sddc
Id string - The OCID of the SDDC that Datastore cluster is associated with.
- State string
- The current state of the Datastore Cluster.
- Dictionary<string, string>
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - Time
Created string - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - Time
Updated string - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
- Availability
Domain string - The availability domain of the Datastore Cluster.
- Capacity
In float64Gbs - Total size of all datastores associated with the datastore cluster in GB.
- Cluster
Id string - The OCID of the VMware Cluster that Datastore cluster is attached to.
- Compartment
Id string - The OCID of the compartment that contains the Datastore.
- Datastore
Cluster stringId - Datastore
Cluster stringType - Type of the datastore cluster.
- Datastore
Ids []string - The OCIDs of the Datastores that belong to the Datastore Cluster
- map[string]string
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - Display
Name string - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- Esxi
Host []stringIds - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- 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 Datastore cluster.
- Sddc
Id string - The OCID of the SDDC that Datastore cluster is associated with.
- State string
- The current state of the Datastore Cluster.
- map[string]string
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - Time
Created string - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - Time
Updated string - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
- availability
Domain String - The availability domain of the Datastore Cluster.
- capacity
In DoubleGbs - Total size of all datastores associated with the datastore cluster in GB.
- cluster
Id String - The OCID of the VMware Cluster that Datastore cluster is attached to.
- compartment
Id String - The OCID of the compartment that contains the Datastore.
- datastore
Cluster StringId - datastore
Cluster StringType - Type of the datastore cluster.
- datastore
Ids List<String> - The OCIDs of the Datastores that belong to the Datastore Cluster
- Map<String,String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - display
Name String - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- esxi
Host List<String>Ids - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- 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 Datastore cluster.
- sddc
Id String - The OCID of the SDDC that Datastore cluster is associated with.
- state String
- The current state of the Datastore Cluster.
- Map<String,String>
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - time
Created String - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - time
Updated String - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
- availability
Domain string - The availability domain of the Datastore Cluster.
- capacity
In numberGbs - Total size of all datastores associated with the datastore cluster in GB.
- cluster
Id string - The OCID of the VMware Cluster that Datastore cluster is attached to.
- compartment
Id string - The OCID of the compartment that contains the Datastore.
- datastore
Cluster stringId - datastore
Cluster stringType - Type of the datastore cluster.
- datastore
Ids string[] - The OCIDs of the Datastores that belong to the Datastore Cluster
- {[key: string]: string}
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - display
Name string - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- esxi
Host string[]Ids - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- {[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 Datastore cluster.
- sddc
Id string - The OCID of the SDDC that Datastore cluster is associated with.
- state string
- The current state of the Datastore Cluster.
- {[key: string]: string}
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - time
Created string - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - time
Updated string - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
- availability_
domain str - The availability domain of the Datastore Cluster.
- capacity_
in_ floatgbs - Total size of all datastores associated with the datastore cluster in GB.
- cluster_
id str - The OCID of the VMware Cluster that Datastore cluster is attached to.
- compartment_
id str - The OCID of the compartment that contains the Datastore.
- datastore_
cluster_ strid - datastore_
cluster_ strtype - Type of the datastore cluster.
- datastore_
ids Sequence[str] - The OCIDs of the Datastores that belong to the Datastore Cluster
- Mapping[str, str]
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - display_
name str - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- esxi_
host_ Sequence[str]ids - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- 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 Datastore cluster.
- sddc_
id str - The OCID of the SDDC that Datastore cluster is associated with.
- state str
- The current state of the Datastore Cluster.
- Mapping[str, str]
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - time_
created str - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - time_
updated str - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
- availability
Domain String - The availability domain of the Datastore Cluster.
- capacity
In NumberGbs - Total size of all datastores associated with the datastore cluster in GB.
- cluster
Id String - The OCID of the VMware Cluster that Datastore cluster is attached to.
- compartment
Id String - The OCID of the compartment that contains the Datastore.
- datastore
Cluster StringId - datastore
Cluster StringType - Type of the datastore cluster.
- datastore
Ids List<String> - The OCIDs of the Datastores that belong to the Datastore Cluster
- Map<String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - display
Name String - A descriptive name for the Datastore Cluster. It must be unique within a SDDC, start with a letter, and contain only letters, digits, whitespaces, dashes and underscores. Avoid entering confidential information.
- esxi
Host List<String>Ids - The OCIDs of the ESXi hosts to attach the datastore to. All ESXi hosts must belong to the same VMware cluster.
- 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 Datastore cluster.
- sddc
Id String - The OCID of the SDDC that Datastore cluster is associated with.
- state String
- The current state of the Datastore Cluster.
- Map<String>
- Usage of system tag keys. These predefined keys are scoped to namespaces. Example:
{orcl-cloud: {free-tier-retain: true}} - time
Created String - The date and time the Datastore Cluster was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - time
Updated String - The date and time the Datastore Cluster was updated, in the format defined by RFC3339.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
ociTerraform Provider.
