Oracle Cloud Infrastructure v1.16.1, Nov 22 23

Oracle Cloud Infrastructure v1.16.1 published on Wednesday, Nov 22, 2023 by Pulumi

oci.Database.getAutonomousDatabaseDataguardAssociation

Explore with Pulumi AI

Oracle Cloud Infrastructure v1.16.1 published on Wednesday, Nov 22, 2023 by Pulumi

Example Usage

using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;

return await Deployment.RunAsync(() => 
{
    var testAutonomousDatabaseDataguardAssociation = Oci.Database.GetAutonomousDatabaseDataguardAssociation.Invoke(new()
    {
        AutonomousDatabaseDataguardAssociationId = oci_database_autonomous_database_dataguard_association.Test_autonomous_database_dataguard_association.Id,
        AutonomousDatabaseId = oci_database_autonomous_database.Test_autonomous_database.Id,
    });

});

package main

import (
	"github.com/pulumi/pulumi-oci/sdk/go/oci/Database"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := Database.GetAutonomousDatabaseDataguardAssociation(ctx, &database.GetAutonomousDatabaseDataguardAssociationArgs{
			AutonomousDatabaseDataguardAssociationId: oci_database_autonomous_database_dataguard_association.Test_autonomous_database_dataguard_association.Id,
			AutonomousDatabaseId:                     oci_database_autonomous_database.Test_autonomous_database.Id,
		}, nil)
		if err != nil {
			return err
		}
		return nil
	})
}

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.GetAutonomousDatabaseDataguardAssociationArgs;
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 testAutonomousDatabaseDataguardAssociation = DatabaseFunctions.getAutonomousDatabaseDataguardAssociation(GetAutonomousDatabaseDataguardAssociationArgs.builder()
            .autonomousDatabaseDataguardAssociationId(oci_database_autonomous_database_dataguard_association.test_autonomous_database_dataguard_association().id())
            .autonomousDatabaseId(oci_database_autonomous_database.test_autonomous_database().id())
            .build());

    }
}

import pulumi
import pulumi_oci as oci

test_autonomous_database_dataguard_association = oci.Database.get_autonomous_database_dataguard_association(autonomous_database_dataguard_association_id=oci_database_autonomous_database_dataguard_association["test_autonomous_database_dataguard_association"]["id"],
    autonomous_database_id=oci_database_autonomous_database["test_autonomous_database"]["id"])

import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";

const testAutonomousDatabaseDataguardAssociation = oci.Database.getAutonomousDatabaseDataguardAssociation({
    autonomousDatabaseDataguardAssociationId: oci_database_autonomous_database_dataguard_association.test_autonomous_database_dataguard_association.id,
    autonomousDatabaseId: oci_database_autonomous_database.test_autonomous_database.id,
});

variables:
  testAutonomousDatabaseDataguardAssociation:
    fn::invoke:
      Function: oci:Database:getAutonomousDatabaseDataguardAssociation
      Arguments:
        autonomousDatabaseDataguardAssociationId: ${oci_database_autonomous_database_dataguard_association.test_autonomous_database_dataguard_association.id}
        autonomousDatabaseId: ${oci_database_autonomous_database.test_autonomous_database.id}

Using getAutonomousDatabaseDataguardAssociation

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 getAutonomousDatabaseDataguardAssociation(args: GetAutonomousDatabaseDataguardAssociationArgs, opts?: InvokeOptions): Promise<GetAutonomousDatabaseDataguardAssociationResult>
function getAutonomousDatabaseDataguardAssociationOutput(args: GetAutonomousDatabaseDataguardAssociationOutputArgs, opts?: InvokeOptions): Output<GetAutonomousDatabaseDataguardAssociationResult>

def get_autonomous_database_dataguard_association(autonomous_database_dataguard_association_id: Optional[str] = None,
                                                  autonomous_database_id: Optional[str] = None,
                                                  opts: Optional[InvokeOptions] = None) -> GetAutonomousDatabaseDataguardAssociationResult
def get_autonomous_database_dataguard_association_output(autonomous_database_dataguard_association_id: Optional[pulumi.Input[str]] = None,
                                                  autonomous_database_id: Optional[pulumi.Input[str]] = None,
                                                  opts: Optional[InvokeOptions] = None) -> Output[GetAutonomousDatabaseDataguardAssociationResult]

func GetAutonomousDatabaseDataguardAssociation(ctx *Context, args *GetAutonomousDatabaseDataguardAssociationArgs, opts ...InvokeOption) (*GetAutonomousDatabaseDataguardAssociationResult, error)
func GetAutonomousDatabaseDataguardAssociationOutput(ctx *Context, args *GetAutonomousDatabaseDataguardAssociationOutputArgs, opts ...InvokeOption) GetAutonomousDatabaseDataguardAssociationResultOutput

> Note: This function is named GetAutonomousDatabaseDataguardAssociation in the Go SDK.

public static class GetAutonomousDatabaseDataguardAssociation 
{
    public static Task<GetAutonomousDatabaseDataguardAssociationResult> InvokeAsync(GetAutonomousDatabaseDataguardAssociationArgs args, InvokeOptions? opts = null)
    public static Output<GetAutonomousDatabaseDataguardAssociationResult> Invoke(GetAutonomousDatabaseDataguardAssociationInvokeArgs args, InvokeOptions? opts = null)
}

public static CompletableFuture<GetAutonomousDatabaseDataguardAssociationResult> getAutonomousDatabaseDataguardAssociation(GetAutonomousDatabaseDataguardAssociationArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet

fn::invoke:
  function: oci:Database/getAutonomousDatabaseDataguardAssociation:getAutonomousDatabaseDataguardAssociation
  arguments:
    # arguments dictionary

The following arguments are supported:

AutonomousDatabaseDataguardAssociationId string: The Autonomous Database Dataguard Association OCID.
AutonomousDatabaseId string: The database OCID.

AutonomousDatabaseDataguardAssociationId string: The Autonomous Database Dataguard Association OCID.
AutonomousDatabaseId string: The database OCID.

autonomousDatabaseDataguardAssociationId String: The Autonomous Database Dataguard Association OCID.
autonomousDatabaseId String: The database OCID.

autonomousDatabaseDataguardAssociationId string: The Autonomous Database Dataguard Association OCID.
autonomousDatabaseId string: The database OCID.

autonomous_database_dataguard_association_id str: The Autonomous Database Dataguard Association OCID.
autonomous_database_id str: The database OCID.

autonomousDatabaseDataguardAssociationId String: The Autonomous Database Dataguard Association OCID.
autonomousDatabaseId String: The database OCID.

getAutonomousDatabaseDataguardAssociation Result

The following output properties are available:

ApplyLag string: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
ApplyRate string: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
AutonomousDatabaseDataguardAssociationId string
AutonomousDatabaseId string: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
Id string: The provider-assigned unique ID for this managed resource.
LifecycleDetails string: Additional information about the current lifecycleState, if available.
PeerAutonomousDatabaseId string: The OCID of the peer Autonomous Database.
PeerAutonomousDatabaseLifeCycleState string: The current state of the Autonomous Dataguard.
PeerRole string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
ProtectionMode string: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
Role string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
State string: The current state of the Autonomous Dataguard.
TimeCreated string: The date and time the Data Guard association was created.
TimeLastRoleChanged string: The date and time when the last role change action happened.

ApplyLag string: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
ApplyRate string: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
AutonomousDatabaseDataguardAssociationId string
AutonomousDatabaseId string: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
Id string: The provider-assigned unique ID for this managed resource.
LifecycleDetails string: Additional information about the current lifecycleState, if available.
PeerAutonomousDatabaseId string: The OCID of the peer Autonomous Database.
PeerAutonomousDatabaseLifeCycleState string: The current state of the Autonomous Dataguard.
PeerRole string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
ProtectionMode string: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
Role string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
State string: The current state of the Autonomous Dataguard.
TimeCreated string: The date and time the Data Guard association was created.
TimeLastRoleChanged string: The date and time when the last role change action happened.

applyLag String: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
applyRate String: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
autonomousDatabaseDataguardAssociationId String
autonomousDatabaseId String: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
id String: The provider-assigned unique ID for this managed resource.
lifecycleDetails String: Additional information about the current lifecycleState, if available.
peerAutonomousDatabaseId String: The OCID of the peer Autonomous Database.
peerAutonomousDatabaseLifeCycleState String: The current state of the Autonomous Dataguard.
peerRole String: The role of the Autonomous Dataguard enabled Autonomous Container Database.
protectionMode String: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
role String: The role of the Autonomous Dataguard enabled Autonomous Container Database.
state String: The current state of the Autonomous Dataguard.
timeCreated String: The date and time the Data Guard association was created.
timeLastRoleChanged String: The date and time when the last role change action happened.

applyLag string: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
applyRate string: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
autonomousDatabaseDataguardAssociationId string
autonomousDatabaseId string: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
id string: The provider-assigned unique ID for this managed resource.
lifecycleDetails string: Additional information about the current lifecycleState, if available.
peerAutonomousDatabaseId string: The OCID of the peer Autonomous Database.
peerAutonomousDatabaseLifeCycleState string: The current state of the Autonomous Dataguard.
peerRole string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
protectionMode string: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
role string: The role of the Autonomous Dataguard enabled Autonomous Container Database.
state string: The current state of the Autonomous Dataguard.
timeCreated string: The date and time the Data Guard association was created.
timeLastRoleChanged string: The date and time when the last role change action happened.

apply_lag str: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
apply_rate str: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
autonomous_database_dataguard_association_id str
autonomous_database_id str: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
id str: The provider-assigned unique ID for this managed resource.
lifecycle_details str: Additional information about the current lifecycleState, if available.
peer_autonomous_database_id str: The OCID of the peer Autonomous Database.
peer_autonomous_database_life_cycle_state str: The current state of the Autonomous Dataguard.
peer_role str: The role of the Autonomous Dataguard enabled Autonomous Container Database.
protection_mode str: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
role str: The role of the Autonomous Dataguard enabled Autonomous Container Database.
state str: The current state of the Autonomous Dataguard.
time_created str: The date and time the Data Guard association was created.
time_last_role_changed str: The date and time when the last role change action happened.

applyLag String: The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database. Example: 9 seconds
applyRate String: The rate at which redo logs are synced between the associated databases. Example: 180 Mb per second
autonomousDatabaseDataguardAssociationId String
autonomousDatabaseId String: The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
id String: The provider-assigned unique ID for this managed resource.
lifecycleDetails String: Additional information about the current lifecycleState, if available.
peerAutonomousDatabaseId String: The OCID of the peer Autonomous Database.
peerAutonomousDatabaseLifeCycleState String: The current state of the Autonomous Dataguard.
peerRole String: The role of the Autonomous Dataguard enabled Autonomous Container Database.
protectionMode String: The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
role String: The role of the Autonomous Dataguard enabled Autonomous Container Database.
state String: The current state of the Autonomous Dataguard.
timeCreated String: The date and time the Data Guard association was created.
timeLastRoleChanged String: The date and time when the last role change action happened.

Package Details

Repository: oci pulumi/pulumi-oci
License: Apache-2.0
Notes: This Pulumi package is based on the oci Terraform Provider.

Oracle Cloud Infrastructure v1.16.1 published on Wednesday, Nov 22, 2023 by Pulumi

pulumi/pulumi-oci

oci.Database.getAutonomousDatabaseDataguardAssociation

On this page

On this page

Example Usage

Using getAutonomousDatabaseDataguardAssociation

getAutonomousDatabaseDataguardAssociation Result

Package Details

On this page

On this page