接口 ConfigurationSyncRequestOrBuilder

所有超级接口:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
所有已知实现类:
ConfigurationSyncRequest, ConfigurationSyncRequest.Builder

public interface ConfigurationSyncRequestOrBuilder extends com.google.protobuf.MessageOrBuilder
  • 方法概要

    修饰符和类型
    方法
    说明
    Current agent service name.
    com.google.protobuf.ByteString
    Current agent service name.
    [Optional] UUID is the unique id to represent the signature of the latest configuration.
    com.google.protobuf.ByteString
    [Optional] UUID is the unique id to represent the signature of the latest configuration.

    从接口继承的方法 com.google.protobuf.MessageLiteOrBuilder

    isInitialized

    从接口继承的方法 com.google.protobuf.MessageOrBuilder

    findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
  • 方法详细资料

    • getService

      String getService()
       Current agent service name.
       
      string service = 1;
      返回:
      The service.
    • getServiceBytes

      com.google.protobuf.ByteString getServiceBytes()
       Current agent service name.
       
      string service = 1;
      返回:
      The bytes for service.
    • getUuid

      String getUuid()
       [Optional]
       UUID is the unique id to represent the signature of the latest configuration.
       The agent usually uses its bootstrap configuration running in default, and this id could be empty when doing the 1st round sync.
       The agent could/is recommended to cache the UUID from the last command, and put it as the next round UUID parameter, 
       then the OAP only returns the empty Commands if no configuration change happenned.
       
      string uuid = 2;
      返回:
      The uuid.
    • getUuidBytes

      com.google.protobuf.ByteString getUuidBytes()
       [Optional]
       UUID is the unique id to represent the signature of the latest configuration.
       The agent usually uses its bootstrap configuration running in default, and this id could be empty when doing the 1st round sync.
       The agent could/is recommended to cache the UUID from the last command, and put it as the next round UUID parameter, 
       then the OAP only returns the empty Commands if no configuration change happenned.
       
      string uuid = 2;
      返回:
      The bytes for uuid.