Namespace DataSciencePrivateEndpointSummary

The OCID of the compartment where you want to create private Endpoint.

The OCID of the user that created the private endpoint.

Data Science resource type.

Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}

A user friendly name. It doesn't have to be unique. Avoid entering confidential information.

Accesing Data Science resource using FQDN.

Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. See Resource Tags. Example: {@code {"Department": "Finance"}}

The OCID of a private endpoint.

Details of the state of a private endpoint.

State of a private endpoint.

An array of network security group OCIDs.

The OCID of a subnet.

Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}

The date and time that the Data Science private endpoint was created, expressed in RFC 3339 timestamp format. Example: {@code 2018-04-03T21:10:29.600Z}

The date and time that the Data Science private endpoint was updated expressed in RFC 3339 timestamp format. Example: {@code 2018-04-03T21:10:29.600Z}