Data Source: oci_core_cpes
This data source provides the list of Cpes in Oracle Cloud Infrastructure Core service.
Lists the customer-premises equipment objects (CPEs) in the specified compartment.
Example Usage
data "oci_core_cpes" "test_cpes" {
	#Required
	compartment_id = var.compartment_id
}
Argument Reference
The following arguments are supported:
- compartment_id- (Required) The OCID of the compartment.
Attributes Reference
The following attributes are exported:
- cpes- The list of cpes.
Cpe Reference
The following attributes are exported:
- compartment_id- The OCID of the compartment containing the CPE.
- cpe_device_shape_id- The OCID of the CPE’s device type. The Networking service maintains a general list of CPE device types (for example, Cisco ASA). For each type, Oracle provides CPE configuration content that can help a network engineer configure the CPE. The OCID uniquely identifies the type of device. To get the OCIDs for the device types on the list, see ListCpeDeviceShapes.- For information about how to generate CPE configuration content for a CPE device type, see: 
- 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.
- 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"}
- id- The CPE’s Oracle ID (OCID).
- ip_address- The public IP address of the on-premises router.
- is_private- Indicates whether this CPE is of type- privateor not.
- time_created- The date and time the CPE was created, in the format defined by RFC3339. Example:- 2016-08-25T21:10:29.600Z