Package com.daml.ledger.api.v1.admin

Class PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder

    • Method Detail

      • getDescriptor

        public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

      • getDescriptorForType

        public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
        Specified by:
        getDescriptorForType in interface com.google.protobuf.Message.Builder
        Specified by:
        getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
        Overrides:
        getDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder>

      • getDefaultInstanceForType

        public PartyManagementServiceOuterClass.UpdatePartyDetailsRequest getDefaultInstanceForType()
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
        Specified by:
        getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

      • hasUpdateMask

        public boolean hasUpdateMask()
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];
        Specified by:
        hasUpdateMask in interface PartyManagementServiceOuterClass.UpdatePartyDetailsRequestOrBuilder
        Returns:
        Whether the updateMask field is set.

      • getUpdateMask

        public com.google.protobuf.FieldMask getUpdateMask()
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];
        Specified by:
        getUpdateMask in interface PartyManagementServiceOuterClass.UpdatePartyDetailsRequestOrBuilder
        Returns:
        The updateMask.

      • setUpdateMask

        public PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder setUpdateMask​(com.google.protobuf.FieldMask value)
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];

      • setUpdateMask

        public PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder setUpdateMask​(com.google.protobuf.FieldMask.Builder builderForValue)
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];

      • mergeUpdateMask

        public PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder mergeUpdateMask​(com.google.protobuf.FieldMask value)
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];

      • clearUpdateMask

        public PartyManagementServiceOuterClass.UpdatePartyDetailsRequest.Builder clearUpdateMask()
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];

      • getUpdateMaskBuilder

        public com.google.protobuf.FieldMask.Builder getUpdateMaskBuilder()
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];

      • getUpdateMaskOrBuilder

        public com.google.protobuf.FieldMaskOrBuilder getUpdateMaskOrBuilder()
         An update mask specifies how and which properties of the ``PartyDetails`` message are to be updated.
 An update mask consists of a set of update paths.
 A valid update path points to a field or a subfield relative to the ``PartyDetails`` message.
 A valid update mask must:
 (1) contain at least one update path,
 (2) contain only valid update paths.
 Fields that can be updated are marked as ``Modifiable``.
 An update path can also point to non-``Modifiable`` fields such as 'party' and 'local_metadata.resource_version'
 because they are used:
 (1) to identify the party details resource subject to the update,
 (2) for concurrent change control.
 An update path can also point to non-``Modifiable`` fields such as 'is_local' and 'display_name'
 as long as the values provided in the update request match the server values.
 Examples of update paths: 'local_metadata.annotations', 'local_metadata'.
 For additional information see the documentation for standard protobuf3's ``google.protobuf.FieldMask``.
 For similar Ledger API see ``com.daml.ledger.api.v1.admin.UpdateUserRequest``.
 Required
        .google.protobuf.FieldMask update_mask = 2 [json_name = "updateMask"];
        Specified by:
        getUpdateMaskOrBuilder in interface PartyManagementServiceOuterClass.UpdatePartyDetailsRequestOrBuilder