The maximum number of CPUs allowed with a 'Bring Your Own License' (BYOL) license type. Any CPU usage above this limit is considered as License Included and billed. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The Minimum number of OCPUs to be made available for this Deployment. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Tags defined for this resource. Each key is predefined and scoped to a namespace.
Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
Metadata about this specific object.
An object's Display Name.
Specifies whether the deployment is used in a production or development/testing environment.
A three-label Fully Qualified Domain Name (FQDN) for a resource.
A simple key-value pair that is applied without any predefined name, type, or scope. Exists for cross-compatibility only.
Example: {@code {\"bar-key\": \"value\"}}
Indicates if auto scaling is enabled for the Deployment's CPU core count.
Flag to allow to configure the 'Bring Your Own License' (BYOL) license type CPU limit. If enabled, the exact number of CPUs must be provided via byolCpuCoreCountLimit.
True if this object is publicly available.
The Oracle license model that applies to a Deployment.
The OCID of a public subnet in the customer tenancy. Can be provided only for public deployments. If provided, the loadbalancer will be created in this subnet instead of the service tenancy. For backward compatibility, this is an optional property. It will become mandatory for public deployments after October 1, 2024.
An array of Network Security Group OCIDs used to define network access for either Deployments or Connections.
An array of local peers of deployment
Security attributes for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Oracle-ZPR\": {\"MaxEgressCount\": {\"value\": \"42\", \"mode\": \"enforce\"}}}}
The OCID of the subnet of the deployment's private endpoint. The subnet must be a private subnet. For backward compatibility, public subnets are allowed until May 31 2025, after which the private subnet will be enforced.
The information to use to update a Deployment.