getAliasesList();
/**
*
* The aliases are a list of other names that this resource can go by.
*
*
* repeated string aliases = 4;
* @return The count of aliases.
*/
int getAliasesCount();
/**
*
* The aliases are a list of other names that this resource can go by.
*
*
* repeated string aliases = 4;
* @param index The index of the element to return.
* @return The aliases at the given index.
*/
java.lang.String getAliases(int index);
/**
*
* The aliases are a list of other names that this resource can go by.
*
*
* repeated string aliases = 4;
* @param index The index of the value to return.
* @return The bytes of the aliases at the given index.
*/
com.google.protobuf.ByteString
getAliasesBytes(int index);
/**
*
* The resource level version. It allows xDS to track the state of individual
* resources.
*
*
* string version = 1;
* @return The version.
*/
java.lang.String getVersion();
/**
*
* The resource level version. It allows xDS to track the state of individual
* resources.
*
*
* string version = 1;
* @return The bytes for version.
*/
com.google.protobuf.ByteString
getVersionBytes();
/**
*
* The resource being tracked.
*
*
* .google.protobuf.Any resource = 2;
* @return Whether the resource field is set.
*/
boolean hasResource();
/**
*
* The resource being tracked.
*
*
* .google.protobuf.Any resource = 2;
* @return The resource.
*/
com.google.protobuf.Any getResource();
/**
*
* The resource being tracked.
*
*
* .google.protobuf.Any resource = 2;
*/
com.google.protobuf.AnyOrBuilder getResourceOrBuilder();
/**
*
* Time-to-live value for the resource. For each resource, a timer is started. The timer is
* reset each time the resource is received with a new TTL. If the resource is received with
* no TTL set, the timer is removed for the resource. Upon expiration of the timer, the
* configuration for the resource will be removed.
* The TTL can be refreshed or changed by sending a response that doesn't change the resource
* version. In this case the resource field does not need to be populated, which allows for
* light-weight "heartbeat" updates to keep a resource with a TTL alive.
* The TTL feature is meant to support configurations that should be removed in the event of
* a management server failure. For example, the feature may be used for fault injection
* testing where the fault injection should be terminated in the event that Envoy loses contact
* with the management server.
*
*
* .google.protobuf.Duration ttl = 6;
* @return Whether the ttl field is set.
*/
boolean hasTtl();
/**
*
* Time-to-live value for the resource. For each resource, a timer is started. The timer is
* reset each time the resource is received with a new TTL. If the resource is received with
* no TTL set, the timer is removed for the resource. Upon expiration of the timer, the
* configuration for the resource will be removed.
* The TTL can be refreshed or changed by sending a response that doesn't change the resource
* version. In this case the resource field does not need to be populated, which allows for
* light-weight "heartbeat" updates to keep a resource with a TTL alive.
* The TTL feature is meant to support configurations that should be removed in the event of
* a management server failure. For example, the feature may be used for fault injection
* testing where the fault injection should be terminated in the event that Envoy loses contact
* with the management server.
*
*
* .google.protobuf.Duration ttl = 6;
* @return The ttl.
*/
com.google.protobuf.Duration getTtl();
/**
*
* Time-to-live value for the resource. For each resource, a timer is started. The timer is
* reset each time the resource is received with a new TTL. If the resource is received with
* no TTL set, the timer is removed for the resource. Upon expiration of the timer, the
* configuration for the resource will be removed.
* The TTL can be refreshed or changed by sending a response that doesn't change the resource
* version. In this case the resource field does not need to be populated, which allows for
* light-weight "heartbeat" updates to keep a resource with a TTL alive.
* The TTL feature is meant to support configurations that should be removed in the event of
* a management server failure. For example, the feature may be used for fault injection
* testing where the fault injection should be terminated in the event that Envoy loses contact
* with the management server.
*
*
* .google.protobuf.Duration ttl = 6;
*/
com.google.protobuf.DurationOrBuilder getTtlOrBuilder();
/**
*
* Cache control properties for the resource.
* [#not-implemented-hide:]
*
*
* .envoy.service.discovery.v3.Resource.CacheControl cache_control = 7;
* @return Whether the cacheControl field is set.
*/
boolean hasCacheControl();
/**
*
* Cache control properties for the resource.
* [#not-implemented-hide:]
*
*
* .envoy.service.discovery.v3.Resource.CacheControl cache_control = 7;
* @return The cacheControl.
*/
io.envoyproxy.envoy.service.discovery.v3.Resource.CacheControl getCacheControl();
/**
*
* Cache control properties for the resource.
* [#not-implemented-hide:]
*
*
* .envoy.service.discovery.v3.Resource.CacheControl cache_control = 7;
*/
io.envoyproxy.envoy.service.discovery.v3.Resource.CacheControlOrBuilder getCacheControlOrBuilder();
/**
*
* The Metadata field can be used to provide additional information for the resource.
* E.g. the trace data for debugging.
*
*
* .envoy.config.core.v3.Metadata metadata = 9;
* @return Whether the metadata field is set.
*/
boolean hasMetadata();
/**
*
* The Metadata field can be used to provide additional information for the resource.
* E.g. the trace data for debugging.
*
*
* .envoy.config.core.v3.Metadata metadata = 9;
* @return The metadata.
*/
io.envoyproxy.envoy.config.core.v3.Metadata getMetadata();
/**
*
* The Metadata field can be used to provide additional information for the resource.
* E.g. the trace data for debugging.
*
*
* .envoy.config.core.v3.Metadata metadata = 9;
*/
io.envoyproxy.envoy.config.core.v3.MetadataOrBuilder getMetadataOrBuilder();
}
