oci_core_drg_attachment_management
This resource provides the Drg Attachment Management resource in Oracle Cloud Infrastructure Core service.
This can be used to update the Drg Attachments of the following types - “IPSEC_TUNNEL”, “REMOTE_PEERING_CONNECTION”, “VIRTUAL_CIRCUIT”,
DRG Attachments for virtual circuits, IPSec tunnels, and remote peering connections are created (and deleted) automatically on your behalf when you create (or delete) the network object. Hence, this management resource is used to update these types of autogenerated DRG Attachments. The user cannot create DRG attachments of these types as needed.
For the purposes of access control, the DRG attachment is automatically placed into the currently selected compartment. For more information about compartments and access control, see Overview of the IAM Service.
Example Usage
resource "oci_core_drg_attachment_management" "test_drg_rpc_attachment" {
#Required
attachment_type = "REMOTE_PEERING_CONNECTION"
compartment_id = var.compartment_ocid
network_id = oci_core_remote_peering_connection.test_rpc.id
drg_id = oci_core_drg.test_drg.id
#Optional
display_name = "MyTestDrgAttachmentForRpc"
drg_route_table_id = oci_core_drg_route_table.test_drg_route_table.id
}
Argument Reference
The following arguments are supported:
attachment_type
- (Required) The type for the network resource attached to the DRG.compartment_id
- (Required) The OCID of the compartment.network_id
- (Optional) The OCID of the resource (virtual circuit, VCN, IPSec tunnel, or remote peering connection) attached to the DRG.defined_tags
- (Optional)(Updatable) 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
- (Optional)(Updatable) A user-friendly name. Does not have to be unique, and it’s changeable. Avoid entering confidential information.drg_id
- (Required) The OCID of the DRG.drg_route_table_id
- (Optional)(Updatable) The OCID of the DRG route table assigned to the DRG attachment.freeform_tags
- (Optional)(Updatable) 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"}
network_details
- (Optional)(Updatable)id
-(Required) The OCID of the network attached to the DRG.ipsec_connection_id
- The IPSec connection that contains the attached IPSec tunnel.route_table_id
(Optional)(Updatable)- The OCID of the route table the DRG attachment is using.
For information about why you would associate a route table with a DRG attachment, see: * Transit Routing: Access to Multiple VCNs in Same Region * Transit Routing: Private Access to Oracle Services *
type
(Required)- The type can be one of these values:IPSEC_TUNNEL
,REMOTE_PEERING_CONNECTION
,VCN
,VIRTUAL_CIRCUIT
route_table_id
(Optional)(Updatable) - The OCID of the route table the DRG attachment is using.
For information about why you would associate a route table with a DRG attachment, see:
* Transit Routing: Access to Multiple VCNs in Same Region
* Transit Routing: Private Access to Oracle Services This field is deprecated. Instead, use the networkDetails
field to view the OCID of the attached resource.
* vcn_id
- (Optional) The OCID of the VCN.
* export_drg_route_distribution_id
(Optional) (Updatable) - The OCID of the export route distribution used to specify how routes in the assigned DRG route table are advertised to the attachment. If this value is null, no routes are advertised through this attachment.
* remove_export_drg_route_distribution_trigger
- (Optional) (Updatable) An optional property when set to true during update disables the export of route Distribution by setting export_drg_route_distribution_id to null.
Attributes Reference
The following attributes are exported:
attachment_type
- The type for the network resource attached to the DRG.compartment_id
- The OCID of the compartment.network_id
- The OCID of the resource (virtual circuit, VCN, IPSec tunnel, or remote peering connection) attached to the DRG.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"}
display_name
- A user-friendly name. Does not have to be unique, and it’s changeable. Avoid entering confidential information.drg_id
- The OCID of the DRG.drg_route_table_id
- The OCID of the DRG route table assigned to the DRG attachment.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"}
network_details
-id
- The OCID of the network attached to the DRG.ipsec_connection_id
- The IPSec connection that contains the attached IPSec tunnel.route_table_id
- The OCID of the route table the DRG attachment is using.type
- The type can be one of these values:IPSEC_TUNNEL
,REMOTE_PEERING_CONNECTION
,VIRTUAL_CIRCUIT
route_table_id
- The OCID of the route table the DRG attachment is using.vcn_id
- The OCID of the VCN.export_drg_route_distribution_id
- The OCID of the export route distribution used to specify how routes in the assigned DRG route table are advertised to the attachment. If this value is null, no routes are advertised through this attachment.remove_export_drg_route_distribution_trigger
- An optional property when set to true during update disables the export of route Distribution by setting export_drg_route_distribution_id to null.is_cross_tenancy
- Indicates whether the DRG attachment and attached network live in a different tenancy than the DRG. Example:false
state
- A filter to return only resources that match the specified lifecycle state. The value is case insensitive.time_created
- The date and time the DRG attachment was created, in the format defined by RFC3339. Example:2016-08-25T21:10:29.600Z