An array of CA bundles that should be used on the Gateway for TLS validation.
The OCID of the resource.
The OCID of the compartment in which the resource is created.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Example: {@code My new resource}
Gateway endpoint type. {@code PUBLIC} will have a public ip address assigned to it, while {@code PRIVATE} will only be accessible on a private IP address on the subnet.
Example: {@code PUBLIC} or {@code PRIVATE}
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: {@code {\"Department\": \"Finance\"}}
An array of Network Security Groups OCIDs associated with this API Gateway.
The OCID of the subnet in which related resources are created.
Information about the new gateway.