oci core remote peering connection

Overview

A remote peering connection (RPC) is an object on a DRG that lets the VCN that is attached to the DRG peer with a VCN in a different region. Peering means that the two VCNs can communicate using private IP addresses, but without the traffic traversing the internet or routing through your on-premises network. For more information, see VCN Peering.

To use any of the API operations, you must be authorized in an IAM policy. If you’re not authorized, talk to an administrator. If you’re an administrator who needs to write policies to give users access, see Getting Started with Policies.

Warning: Oracle recommends that you avoid using any confidential information when you supply string values using the API.

This documentation is generated from the Ruby OCI SDK.

Attributes

absent_states

The OCI states, puppet will detect as the resource being absent.

Back to overview of oci_core_remote_peering_connection

compartment

The Puppet name of the resource identified by compartment_id.

See the documentation of compartment_id for all details.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

compartment_id

The OCID of the compartment that contains the object.

Rather use the property compartment instead of a direct OCID reference.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

defined_tags

Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.

Example: {"Operations": {"CostCenter": "42"}}

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of oci_core_remote_peering_connection

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of oci_core_remote_peering_connection

drg

The Puppet name of the resource identified by drg_id.

See the documentation of drg_id for all details.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

drg_id

The OCID of the DRG the RPC belongs to. Rather use the property drg instead of a direct OCID reference.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of oci_core_remote_peering_connection

freeform_tags

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"}

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

id

The OCID of the resource. This is a read-only property.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

is_cross_tenancy_peering

Whether the VCN at the other end of the peering is in a different tenancy.

Example: false

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

lifecycle_state

The RPC’s current lifecycle state.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

name

The full name of the object.

Back to overview of oci_core_remote_peering_connection

oci_timeout

The maximum time to wait for the OCI resource to be in the ready state.

Back to overview of oci_core_remote_peering_connection

oci_wait_interval

The interval beween calls to OCI to check if a resource is in the ready state.

Back to overview of oci_core_remote_peering_connection

peer

The Puppet name of the resource identified by peer_id.

See the documentation of peer_id for all details.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

peer_id

If this RPC is peered, this value is the OCID of the other RPC. Rather use the property peer instead of a direct OCID reference.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

peer_region_name

If this RPC is peered, this value is the region that contains the other RPC.

Example: us-ashburn-1

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

peer_tenancy

The Puppet name of the resource identified by peer_tenancy_id.

See the documentation of peer_tenancy_id for all details.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

peer_tenancy_id

If this RPC is peered, this value is the OCID of the other RPC’s tenancy. Rather use the property peer_tenancy instead of a direct OCID reference.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

peering_status

Whether the RPC is peered with another RPC. NEW means the RPC has not yet been peered. PENDING means the peering is being established. REVOKED means the RPC at the other end of the peering has been deleted.

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection

present_states

The OCI states, puppet will detect as the resource being present.

Back to overview of oci_core_remote_peering_connection

provider

The specific backend to use for this oci_core_remote_peering_connection resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

sdk

This provider uses the Oracle Ruby OCI SDK to do its work.

Back to overview of oci_core_remote_peering_connection

remote_peering_connection_name

The name of the remote_peering_connection.

Back to overview of oci_core_remote_peering_connection

synchronized

Specifies if Puppet waits for OCI actions to be ready before moving on to an other resource.

Back to overview of oci_core_remote_peering_connection

tenant

The tenant for this resource.

Back to overview of oci_core_remote_peering_connection

time_created

The date and time the RPC was created, in the format defined by RFC3339.

Example: 2016-08-25T21:10:29.600Z

This documentation is generated from the Ruby OCI SDK.

Back to overview of oci_core_remote_peering_connection