The OCID of the compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Description of the resource. It can be changed after creation. Avoid entering confidential information.
Example: {@code This is my new resource}
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The DNS hostnames of the virtual service that is used by its callers. Wildcard hostnames are supported in the prefix form. Examples of valid hostnames are "www.example.com\", ".example.com", ".com". Can be omitted if the virtual service will only have TCP virtual deployments.
The OCID of the service mesh in which this virtual service is created.
A user-friendly name. The name has to be unique within the same service mesh and cannot be changed after creation. Avoid entering confidential information.
Example: {@code My unique resource name}
The information about the new VirtualService.