Package software.amazon.awssdk.services.codecommit

Interface CodeCommitAsyncClient

All Superinterfaces:
AutoCloseable, AwsClient, SdkAutoCloseable, SdkClient
@Generated("software.amazon.awssdk:codegen") @ThreadSafe public interface CodeCommitAsyncClient extends AwsClient
Service client for accessing CodeCommit asynchronously. This can be created using the static builder() method.The asynchronous client performs non-blocking I/O when configured with any SdkAsyncHttpClient supported in the SDK. However, full non-blocking is not guaranteed as the async client may perform blocking calls in some cases such as credentials retrieval and endpoint discovery as part of the async API call. CodeCommit

This is the CodeCommit API Reference. This reference provides descriptions of the operations and data types for CodeCommit API along with usage examples.

You can use the CodeCommit API to work with the following objects:

Repositories, by calling the following:

  • BatchGetRepositories, which returns information about one or more repositories associated with your Amazon Web Services account.

  • CreateRepository, which creates an CodeCommit repository.

  • DeleteRepository, which deletes an CodeCommit repository.

  • GetRepository, which returns information about a specified repository.

  • ListRepositories, which lists all CodeCommit repositories associated with your Amazon Web Services account.

  • UpdateRepositoryDescription, which sets or updates the description of the repository.

  • UpdateRepositoryEncryptionKey, which updates the Key Management Service encryption key used to encrypt and decrypt a repository.

  • UpdateRepositoryName, which changes the name of the repository. If you change the name of a repository, no other users of that repository can access it until you send them the new HTTPS or SSH URL to use.

Branches, by calling the following:

  • CreateBranch, which creates a branch in a specified repository.

  • DeleteBranch, which deletes the specified branch in a repository unless it is the default branch.

  • GetBranch, which returns information about a specified branch.

  • ListBranches, which lists all branches for a specified repository.

  • UpdateDefaultBranch, which changes the default branch for a repository.

Files, by calling the following:

  • DeleteFile, which deletes the content of a specified file from a specified branch.

  • GetBlob, which returns the base-64 encoded content of an individual Git blob object in a repository.

  • GetFile, which returns the base-64 encoded content of a specified file.

  • GetFolder, which returns the contents of a specified folder or directory.

  • ListFileCommitHistory, which retrieves a list of commits and changes to a specified file.

  • PutFile, which adds or modifies a single file in a specified repository and branch.

Commits, by calling the following:

  • BatchGetCommits, which returns information about one or more commits in a repository.

  • CreateCommit, which creates a commit for changes to a repository.

  • GetCommit, which returns information about a commit, including commit messages and author and committer information.

  • GetDifferences, which returns information about the differences in a valid commit specifier (such as a branch, tag, HEAD, commit ID, or other fully qualified reference).

Merges, by calling the following:

  • BatchDescribeMergeConflicts, which returns information about conflicts in a merge between commits in a repository.

  • CreateUnreferencedMergeCommit, which creates an unreferenced commit between two branches or commits for the purpose of comparing them and identifying any potential conflicts.

  • DescribeMergeConflicts, which returns information about merge conflicts between the base, source, and destination versions of a file in a potential merge.

  • GetMergeCommit, which returns information about the merge between a source and destination commit.

  • GetMergeConflicts, which returns information about merge conflicts between the source and destination branch in a pull request.

  • GetMergeOptions, which returns information about the available merge options between two branches or commit specifiers.

  • MergeBranchesByFastForward, which merges two branches using the fast-forward merge option.

  • MergeBranchesBySquash, which merges two branches using the squash merge option.

  • MergeBranchesByThreeWay, which merges two branches using the three-way merge option.

Pull requests, by calling the following:

Approval rule templates, by calling the following:

Comments in a repository, by calling the following:

Tags used to tag resources in CodeCommit (not Git tags), by calling the following:

  • ListTagsForResource, which gets information about Amazon Web Servicestags for a specified Amazon Resource Name (ARN) in CodeCommit.

  • TagResource, which adds or updates tags for a resource in CodeCommit.

  • UntagResource, which removes tags for a resource in CodeCommit.

Triggers, by calling the following:

  • GetRepositoryTriggers, which returns information about triggers configured for a repository.

  • PutRepositoryTriggers, which replaces all triggers for a repository and can be used to create or delete triggers.

  • TestRepositoryTriggers, which tests the functionality of a repository trigger by sending data to the trigger target.

For information about how to use CodeCommit, see the CodeCommit User Guide.

  • Field Details

  • Method Details

    • associateApprovalRuleTemplateWithRepository

      default CompletableFuture<AssociateApprovalRuleTemplateWithRepositoryResponse> associateApprovalRuleTemplateWithRepository(AssociateApprovalRuleTemplateWithRepositoryRequest associateApprovalRuleTemplateWithRepositoryRequest)

      Creates an association between an approval rule template and a specified repository. Then, the next time a pull request is created in the repository where the destination reference (if specified) matches the destination reference (branch) for the pull request, an approval rule that matches the template conditions is automatically created for that pull request. If no destination references are specified in the template, an approval rule that matches the template contents is created for all pull requests in that repository.

      Parameters:
      associateApprovalRuleTemplateWithRepositoryRequest -
      Returns:
      A Java Future containing the result of the AssociateApprovalRuleTemplateWithRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • MaximumRuleTemplatesAssociatedWithRepositoryException The maximum number of approval rule templates for a repository has been exceeded. You cannot associate more than 25 approval rule templates with a repository.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • associateApprovalRuleTemplateWithRepository

      default CompletableFuture<AssociateApprovalRuleTemplateWithRepositoryResponse> associateApprovalRuleTemplateWithRepository(Consumer<AssociateApprovalRuleTemplateWithRepositoryRequest.Builder> associateApprovalRuleTemplateWithRepositoryRequest)

      Creates an association between an approval rule template and a specified repository. Then, the next time a pull request is created in the repository where the destination reference (if specified) matches the destination reference (branch) for the pull request, an approval rule that matches the template conditions is automatically created for that pull request. If no destination references are specified in the template, an approval rule that matches the template contents is created for all pull requests in that repository.


      This is a convenience which creates an instance of the AssociateApprovalRuleTemplateWithRepositoryRequest.Builder avoiding the need to create one manually via AssociateApprovalRuleTemplateWithRepositoryRequest.builder()

      Parameters:
      associateApprovalRuleTemplateWithRepositoryRequest - A Consumer that will call methods on AssociateApprovalRuleTemplateWithRepositoryRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the AssociateApprovalRuleTemplateWithRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • MaximumRuleTemplatesAssociatedWithRepositoryException The maximum number of approval rule templates for a repository has been exceeded. You cannot associate more than 25 approval rule templates with a repository.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchAssociateApprovalRuleTemplateWithRepositories

      default CompletableFuture<BatchAssociateApprovalRuleTemplateWithRepositoriesResponse> batchAssociateApprovalRuleTemplateWithRepositories(BatchAssociateApprovalRuleTemplateWithRepositoriesRequest batchAssociateApprovalRuleTemplateWithRepositoriesRequest)

      Creates an association between an approval rule template and one or more specified repositories.

      Parameters:
      batchAssociateApprovalRuleTemplateWithRepositoriesRequest -
      Returns:
      A Java Future containing the result of the BatchAssociateApprovalRuleTemplateWithRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchAssociateApprovalRuleTemplateWithRepositories

      default CompletableFuture<BatchAssociateApprovalRuleTemplateWithRepositoriesResponse> batchAssociateApprovalRuleTemplateWithRepositories(Consumer<BatchAssociateApprovalRuleTemplateWithRepositoriesRequest.Builder> batchAssociateApprovalRuleTemplateWithRepositoriesRequest)

      Creates an association between an approval rule template and one or more specified repositories.


      This is a convenience which creates an instance of the BatchAssociateApprovalRuleTemplateWithRepositoriesRequest.Builder avoiding the need to create one manually via BatchAssociateApprovalRuleTemplateWithRepositoriesRequest.builder()

      Parameters:
      batchAssociateApprovalRuleTemplateWithRepositoriesRequest - A Consumer that will call methods on BatchAssociateApprovalRuleTemplateWithRepositoriesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchAssociateApprovalRuleTemplateWithRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchDescribeMergeConflicts

      default CompletableFuture<BatchDescribeMergeConflictsResponse> batchDescribeMergeConflicts(BatchDescribeMergeConflictsRequest batchDescribeMergeConflictsRequest)

      Returns information about one or more merge conflicts in the attempted merge of two commit specifiers using the squash or three-way merge strategy.

      Parameters:
      batchDescribeMergeConflictsRequest -
      Returns:
      A Java Future containing the result of the BatchDescribeMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchDescribeMergeConflicts

      default CompletableFuture<BatchDescribeMergeConflictsResponse> batchDescribeMergeConflicts(Consumer<BatchDescribeMergeConflictsRequest.Builder> batchDescribeMergeConflictsRequest)

      Returns information about one or more merge conflicts in the attempted merge of two commit specifiers using the squash or three-way merge strategy.


      This is a convenience which creates an instance of the BatchDescribeMergeConflictsRequest.Builder avoiding the need to create one manually via BatchDescribeMergeConflictsRequest.builder()

      Parameters:
      batchDescribeMergeConflictsRequest - A Consumer that will call methods on BatchDescribeMergeConflictsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchDescribeMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchDisassociateApprovalRuleTemplateFromRepositories

      default CompletableFuture<BatchDisassociateApprovalRuleTemplateFromRepositoriesResponse> batchDisassociateApprovalRuleTemplateFromRepositories(BatchDisassociateApprovalRuleTemplateFromRepositoriesRequest batchDisassociateApprovalRuleTemplateFromRepositoriesRequest)

      Removes the association between an approval rule template and one or more specified repositories.

      Parameters:
      batchDisassociateApprovalRuleTemplateFromRepositoriesRequest -
      Returns:
      A Java Future containing the result of the BatchDisassociateApprovalRuleTemplateFromRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchDisassociateApprovalRuleTemplateFromRepositories

      default CompletableFuture<BatchDisassociateApprovalRuleTemplateFromRepositoriesResponse> batchDisassociateApprovalRuleTemplateFromRepositories(Consumer<BatchDisassociateApprovalRuleTemplateFromRepositoriesRequest.Builder> batchDisassociateApprovalRuleTemplateFromRepositoriesRequest)

      Removes the association between an approval rule template and one or more specified repositories.


      This is a convenience which creates an instance of the BatchDisassociateApprovalRuleTemplateFromRepositoriesRequest.Builder avoiding the need to create one manually via BatchDisassociateApprovalRuleTemplateFromRepositoriesRequest.builder()

      Parameters:
      batchDisassociateApprovalRuleTemplateFromRepositoriesRequest - A Consumer that will call methods on BatchDisassociateApprovalRuleTemplateFromRepositoriesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchDisassociateApprovalRuleTemplateFromRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchGetCommits

      default CompletableFuture<BatchGetCommitsResponse> batchGetCommits(BatchGetCommitsRequest batchGetCommitsRequest)

      Returns information about the contents of one or more commits in a repository.

      Parameters:
      batchGetCommitsRequest -
      Returns:
      A Java Future containing the result of the BatchGetCommits operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommitIdsListRequiredException A list of commit IDs is required, but was either not specified or the list was empty.
      • CommitIdsLimitExceededException The maximum number of allowed commit IDs in a batch request is 100. Verify that your batch requests contains no more than 100 commit IDs, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchGetCommits

      default CompletableFuture<BatchGetCommitsResponse> batchGetCommits(Consumer<BatchGetCommitsRequest.Builder> batchGetCommitsRequest)

      Returns information about the contents of one or more commits in a repository.


      This is a convenience which creates an instance of the BatchGetCommitsRequest.Builder avoiding the need to create one manually via BatchGetCommitsRequest.builder()

      Parameters:
      batchGetCommitsRequest - A Consumer that will call methods on BatchGetCommitsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the BatchGetCommits operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommitIdsListRequiredException A list of commit IDs is required, but was either not specified or the list was empty.
      • CommitIdsLimitExceededException The maximum number of allowed commit IDs in a batch request is 100. Verify that your batch requests contains no more than 100 commit IDs, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchGetRepositories

      default CompletableFuture<BatchGetRepositoriesResponse> batchGetRepositories(BatchGetRepositoriesRequest batchGetRepositoriesRequest)

      Returns information about one or more repositories.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.

      Parameters:
      batchGetRepositoriesRequest - Represents the input of a batch get repositories operation.
      Returns:
      A Java Future containing the result of the BatchGetRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • batchGetRepositories

      default CompletableFuture<BatchGetRepositoriesResponse> batchGetRepositories(Consumer<BatchGetRepositoriesRequest.Builder> batchGetRepositoriesRequest)

      Returns information about one or more repositories.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.


      This is a convenience which creates an instance of the BatchGetRepositoriesRequest.Builder avoiding the need to create one manually via BatchGetRepositoriesRequest.builder()

      Parameters:
      batchGetRepositoriesRequest - A Consumer that will call methods on BatchGetRepositoriesRequest.Builder to create a request. Represents the input of a batch get repositories operation.
      Returns:
      A Java Future containing the result of the BatchGetRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNamesRequiredException At least one repository name object is required, but was not specified.
      • MaximumRepositoryNamesExceededException The maximum number of allowed repository names was exceeded. Currently, this number is 100.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createApprovalRuleTemplate

      default CompletableFuture<CreateApprovalRuleTemplateResponse> createApprovalRuleTemplate(CreateApprovalRuleTemplateRequest createApprovalRuleTemplateRequest)

      Creates a template for approval rules that can then be associated with one or more repositories in your Amazon Web Services account. When you associate a template with a repository, CodeCommit creates an approval rule that matches the conditions of the template for all pull requests that meet the conditions of the template. For more information, see AssociateApprovalRuleTemplateWithRepository.

      Parameters:
      createApprovalRuleTemplateRequest -
      Returns:
      A Java Future containing the result of the CreateApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameAlreadyExistsException You cannot create an approval rule template with that name because a template with that name already exists in this Amazon Web Services Region for your Amazon Web Services account. Approval rule template names must be unique.
      • ApprovalRuleTemplateContentRequiredException The content for the approval rule template is empty. You must provide some content for an approval rule template. The content cannot be null.
      • InvalidApprovalRuleTemplateContentException The content of the approval rule template is not valid.
      • InvalidApprovalRuleTemplateDescriptionException The description for the approval rule template is not valid because it exceeds the maximum characters allowed for a description. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • NumberOfRuleTemplatesExceededException The maximum number of approval rule templates has been exceeded for this Amazon Web Services Region.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createApprovalRuleTemplate

      default CompletableFuture<CreateApprovalRuleTemplateResponse> createApprovalRuleTemplate(Consumer<CreateApprovalRuleTemplateRequest.Builder> createApprovalRuleTemplateRequest)

      Creates a template for approval rules that can then be associated with one or more repositories in your Amazon Web Services account. When you associate a template with a repository, CodeCommit creates an approval rule that matches the conditions of the template for all pull requests that meet the conditions of the template. For more information, see AssociateApprovalRuleTemplateWithRepository.


      This is a convenience which creates an instance of the CreateApprovalRuleTemplateRequest.Builder avoiding the need to create one manually via CreateApprovalRuleTemplateRequest.builder()

      Parameters:
      createApprovalRuleTemplateRequest - A Consumer that will call methods on CreateApprovalRuleTemplateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameAlreadyExistsException You cannot create an approval rule template with that name because a template with that name already exists in this Amazon Web Services Region for your Amazon Web Services account. Approval rule template names must be unique.
      • ApprovalRuleTemplateContentRequiredException The content for the approval rule template is empty. You must provide some content for an approval rule template. The content cannot be null.
      • InvalidApprovalRuleTemplateContentException The content of the approval rule template is not valid.
      • InvalidApprovalRuleTemplateDescriptionException The description for the approval rule template is not valid because it exceeds the maximum characters allowed for a description. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • NumberOfRuleTemplatesExceededException The maximum number of approval rule templates has been exceeded for this Amazon Web Services Region.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createBranch

      default CompletableFuture<CreateBranchResponse> createBranch(CreateBranchRequest createBranchRequest)

      Creates a branch in a repository and points the branch to a commit.

      Calling the create branch operation does not set a repository's default branch. To do this, call the update default branch operation.

      Parameters:
      createBranchRequest - Represents the input of a create branch operation.
      Returns:
      A Java Future containing the result of the CreateBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameExistsException Cannot create the branch with the specified name because the commit conflicts with an existing branch with the same name. Branch names must be unique.
      • InvalidBranchNameException The specified reference name is not valid.
      • CommitIdRequiredException A commit ID was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitIdException The specified commit ID is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createBranch

      default CompletableFuture<CreateBranchResponse> createBranch(Consumer<CreateBranchRequest.Builder> createBranchRequest)

      Creates a branch in a repository and points the branch to a commit.

      Calling the create branch operation does not set a repository's default branch. To do this, call the update default branch operation.


      This is a convenience which creates an instance of the CreateBranchRequest.Builder avoiding the need to create one manually via CreateBranchRequest.builder()

      Parameters:
      createBranchRequest - A Consumer that will call methods on CreateBranchRequest.Builder to create a request. Represents the input of a create branch operation.
      Returns:
      A Java Future containing the result of the CreateBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameExistsException Cannot create the branch with the specified name because the commit conflicts with an existing branch with the same name. Branch names must be unique.
      • InvalidBranchNameException The specified reference name is not valid.
      • CommitIdRequiredException A commit ID was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitIdException The specified commit ID is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createCommit

      default CompletableFuture<CreateCommitResponse> createCommit(CreateCommitRequest createCommitRequest)

      Creates a commit for a repository on the tip of a specified branch.

      Parameters:
      createCommitRequest -
      Returns:
      A Java Future containing the result of the CreateCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • FileEntryRequiredException The commit cannot be created because no files have been specified as added, updated, or changed (PutFile or DeleteFile) for the commit.
      • MaximumFileEntriesExceededException The number of specified files to change as part of this commit exceeds the maximum number of files that can be changed in a single commit. Consider using a Git client for these changes.
      • PutFileEntryConflictException The commit cannot be created because one or more files specified in the commit reference both a file and a folder.
      • SourceFileOrContentRequiredException The commit cannot be created because no source files or file content have been specified for the commit.
      • FileContentAndSourceFileSpecifiedException The commit cannot be created because both a source file and file content have been specified for the same file. You cannot provide both. Either specify a source file or provide the file content directly.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • SamePathRequestException The commit cannot be created because one or more changes in this commit duplicate actions in the same file path. For example, you cannot make the same delete request to the same file in the same file path twice, or make a delete request and a move request to the same file as part of the same commit.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • InvalidDeletionParameterException The specified deletion parameter is not valid.
      • RestrictedSourceFileException The commit cannot be created because one of the changes specifies copying or moving a .gitkeep file.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • NoChangeException The commit cannot be created because no changes will be made to the repository as a result of this commit. A commit must contain at least one change.
      • FileNameConflictsWithDirectoryNameException A file cannot be added to the repository because the specified file name has the same name as a directory in this repository. Either provide another name for the file, or add the file in a directory that does not match the file name.
      • DirectoryNameConflictsWithFileNameException A file cannot be added to the repository because the specified path name has the same name as a file that already exists in this repository. Either provide a different name for the file, or specify a different path for the file.
      • FilePathConflictsWithSubmodulePathException The commit cannot be created because a specified file path points to a submodule. Verify that the destination files have valid file paths that do not point to a submodule.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createCommit

      default CompletableFuture<CreateCommitResponse> createCommit(Consumer<CreateCommitRequest.Builder> createCommitRequest)

      Creates a commit for a repository on the tip of a specified branch.


      This is a convenience which creates an instance of the CreateCommitRequest.Builder avoiding the need to create one manually via CreateCommitRequest.builder()

      Parameters:
      createCommitRequest - A Consumer that will call methods on CreateCommitRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • FileEntryRequiredException The commit cannot be created because no files have been specified as added, updated, or changed (PutFile or DeleteFile) for the commit.
      • MaximumFileEntriesExceededException The number of specified files to change as part of this commit exceeds the maximum number of files that can be changed in a single commit. Consider using a Git client for these changes.
      • PutFileEntryConflictException The commit cannot be created because one or more files specified in the commit reference both a file and a folder.
      • SourceFileOrContentRequiredException The commit cannot be created because no source files or file content have been specified for the commit.
      • FileContentAndSourceFileSpecifiedException The commit cannot be created because both a source file and file content have been specified for the same file. You cannot provide both. Either specify a source file or provide the file content directly.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • SamePathRequestException The commit cannot be created because one or more changes in this commit duplicate actions in the same file path. For example, you cannot make the same delete request to the same file in the same file path twice, or make a delete request and a move request to the same file as part of the same commit.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • InvalidDeletionParameterException The specified deletion parameter is not valid.
      • RestrictedSourceFileException The commit cannot be created because one of the changes specifies copying or moving a .gitkeep file.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • NoChangeException The commit cannot be created because no changes will be made to the repository as a result of this commit. A commit must contain at least one change.
      • FileNameConflictsWithDirectoryNameException A file cannot be added to the repository because the specified file name has the same name as a directory in this repository. Either provide another name for the file, or add the file in a directory that does not match the file name.
      • DirectoryNameConflictsWithFileNameException A file cannot be added to the repository because the specified path name has the same name as a file that already exists in this repository. Either provide a different name for the file, or specify a different path for the file.
      • FilePathConflictsWithSubmodulePathException The commit cannot be created because a specified file path points to a submodule. Verify that the destination files have valid file paths that do not point to a submodule.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createPullRequest

      default CompletableFuture<CreatePullRequestResponse> createPullRequest(CreatePullRequestRequest createPullRequestRequest)

      Creates a pull request in the specified repository.

      Parameters:
      createPullRequestRequest -
      Returns:
      A Java Future containing the result of the CreatePullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • ReferenceNameRequiredException A reference name is required, but none was provided.
      • InvalidReferenceNameException The specified reference name format is not valid. Reference names must conform to the Git references format (for example, refs/heads/main). For more information, see Git Internals - Git References or consult your Git documentation.
      • ReferenceDoesNotExistException The specified reference does not exist. You must provide a full commit ID.
      • ReferenceTypeNotSupportedException The specified reference is not a supported type.
      • TitleRequiredException A pull request title is required. It cannot be empty or null.
      • InvalidTitleException The title of the pull request is not valid. Pull request titles cannot exceed 100 characters in length.
      • InvalidDescriptionException The pull request description is not valid. Descriptions cannot be more than 1,000 characters.
      • TargetsRequiredException An array of target objects is required. It cannot be empty or null.
      • InvalidTargetsException The targets for the pull request is not valid or not in a valid format. Targets are a list of target objects. Each target object must contain the full values for the repository name, source branch, and destination branch for a pull request.
      • TargetRequiredException A pull request target is required. It cannot be empty or null. A pull request target must contain the full values for the repository name, source branch, and destination branch for the pull request.
      • InvalidTargetException The target for the pull request is not valid. A target must contain the full values for the repository name, source branch, and destination branch for the pull request.
      • MultipleRepositoriesInPullRequestException You cannot include more than one repository in a pull request. Make sure you have specified only one repository name in your request, and then try again.
      • MaximumOpenPullRequestsExceededException You cannot create the pull request because the repository has too many open pull requests. The maximum number of open pull requests for a repository is 1,000. Close one or more open pull requests, and then try again.
      • SourceAndDestinationAreSameException The source branch and destination branch for the pull request are the same. You must specify different branches for the source and destination.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createPullRequest

      default CompletableFuture<CreatePullRequestResponse> createPullRequest(Consumer<CreatePullRequestRequest.Builder> createPullRequestRequest)

      Creates a pull request in the specified repository.


      This is a convenience which creates an instance of the CreatePullRequestRequest.Builder avoiding the need to create one manually via CreatePullRequestRequest.builder()

      Parameters:
      createPullRequestRequest - A Consumer that will call methods on CreatePullRequestRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreatePullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • ReferenceNameRequiredException A reference name is required, but none was provided.
      • InvalidReferenceNameException The specified reference name format is not valid. Reference names must conform to the Git references format (for example, refs/heads/main). For more information, see Git Internals - Git References or consult your Git documentation.
      • ReferenceDoesNotExistException The specified reference does not exist. You must provide a full commit ID.
      • ReferenceTypeNotSupportedException The specified reference is not a supported type.
      • TitleRequiredException A pull request title is required. It cannot be empty or null.
      • InvalidTitleException The title of the pull request is not valid. Pull request titles cannot exceed 100 characters in length.
      • InvalidDescriptionException The pull request description is not valid. Descriptions cannot be more than 1,000 characters.
      • TargetsRequiredException An array of target objects is required. It cannot be empty or null.
      • InvalidTargetsException The targets for the pull request is not valid or not in a valid format. Targets are a list of target objects. Each target object must contain the full values for the repository name, source branch, and destination branch for a pull request.
      • TargetRequiredException A pull request target is required. It cannot be empty or null. A pull request target must contain the full values for the repository name, source branch, and destination branch for the pull request.
      • InvalidTargetException The target for the pull request is not valid. A target must contain the full values for the repository name, source branch, and destination branch for the pull request.
      • MultipleRepositoriesInPullRequestException You cannot include more than one repository in a pull request. Make sure you have specified only one repository name in your request, and then try again.
      • MaximumOpenPullRequestsExceededException You cannot create the pull request because the repository has too many open pull requests. The maximum number of open pull requests for a repository is 1,000. Close one or more open pull requests, and then try again.
      • SourceAndDestinationAreSameException The source branch and destination branch for the pull request are the same. You must specify different branches for the source and destination.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createPullRequestApprovalRule

      default CompletableFuture<CreatePullRequestApprovalRuleResponse> createPullRequestApprovalRule(CreatePullRequestApprovalRuleRequest createPullRequestApprovalRuleRequest)

      Creates an approval rule for a pull request.

      Parameters:
      createPullRequestApprovalRuleRequest -
      Returns:
      A Java Future containing the result of the CreatePullRequestApprovalRule operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • ApprovalRuleNameAlreadyExistsException An approval rule with that name already exists. Approval rule names must be unique within the scope of a pull request.
      • ApprovalRuleContentRequiredException The content for the approval rule is empty. You must provide some content for an approval rule. The content cannot be null.
      • InvalidApprovalRuleContentException The content for the approval rule is not valid.
      • NumberOfRulesExceededException The approval rule cannot be added. The pull request has the maximum number of approval rules associated with it.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createPullRequestApprovalRule

      default CompletableFuture<CreatePullRequestApprovalRuleResponse> createPullRequestApprovalRule(Consumer<CreatePullRequestApprovalRuleRequest.Builder> createPullRequestApprovalRuleRequest)

      Creates an approval rule for a pull request.


      This is a convenience which creates an instance of the CreatePullRequestApprovalRuleRequest.Builder avoiding the need to create one manually via CreatePullRequestApprovalRuleRequest.builder()

      Parameters:
      createPullRequestApprovalRuleRequest - A Consumer that will call methods on CreatePullRequestApprovalRuleRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreatePullRequestApprovalRule operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • ApprovalRuleNameAlreadyExistsException An approval rule with that name already exists. Approval rule names must be unique within the scope of a pull request.
      • ApprovalRuleContentRequiredException The content for the approval rule is empty. You must provide some content for an approval rule. The content cannot be null.
      • InvalidApprovalRuleContentException The content for the approval rule is not valid.
      • NumberOfRulesExceededException The approval rule cannot be added. The pull request has the maximum number of approval rules associated with it.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createRepository

      default CompletableFuture<CreateRepositoryResponse> createRepository(CreateRepositoryRequest createRepositoryRequest)

      Creates a new, empty repository.

      Parameters:
      createRepositoryRequest - Represents the input of a create repository operation.
      Returns:
      A Java Future containing the result of the CreateRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameExistsException The specified repository name already exists.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidRepositoryDescriptionException The specified repository description is not valid.
      • RepositoryLimitExceededException A repository resource limit was exceeded.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • EncryptionKeyInvalidIdException The Key Management Service encryption key is not valid.
      • EncryptionKeyInvalidUsageException A KMS encryption key was used to try and encrypt or decrypt a repository, but either the repository or the key was not in a valid state to support the operation.
      • InvalidTagsMapException The map of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createRepository

      default CompletableFuture<CreateRepositoryResponse> createRepository(Consumer<CreateRepositoryRequest.Builder> createRepositoryRequest)

      Creates a new, empty repository.


      This is a convenience which creates an instance of the CreateRepositoryRequest.Builder avoiding the need to create one manually via CreateRepositoryRequest.builder()

      Parameters:
      createRepositoryRequest - A Consumer that will call methods on CreateRepositoryRequest.Builder to create a request. Represents the input of a create repository operation.
      Returns:
      A Java Future containing the result of the CreateRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameExistsException The specified repository name already exists.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidRepositoryDescriptionException The specified repository description is not valid.
      • RepositoryLimitExceededException A repository resource limit was exceeded.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • EncryptionKeyInvalidIdException The Key Management Service encryption key is not valid.
      • EncryptionKeyInvalidUsageException A KMS encryption key was used to try and encrypt or decrypt a repository, but either the repository or the key was not in a valid state to support the operation.
      • InvalidTagsMapException The map of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createUnreferencedMergeCommit

      default CompletableFuture<CreateUnreferencedMergeCommitResponse> createUnreferencedMergeCommit(CreateUnreferencedMergeCommitRequest createUnreferencedMergeCommitRequest)

      Creates an unreferenced commit that represents the result of merging two branches using a specified merge strategy. This can help you determine the outcome of a potential merge. This API cannot be used with the fast-forward merge strategy because that strategy does not create a merge commit.

      This unreferenced merge commit can only be accessed using the GetCommit API or through git commands such as git fetch. To retrieve this commit, you must specify its commit ID or otherwise reference it.

      Parameters:
      createUnreferencedMergeCommitRequest -
      Returns:
      A Java Future containing the result of the CreateUnreferencedMergeCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createUnreferencedMergeCommit

      default CompletableFuture<CreateUnreferencedMergeCommitResponse> createUnreferencedMergeCommit(Consumer<CreateUnreferencedMergeCommitRequest.Builder> createUnreferencedMergeCommitRequest)

      Creates an unreferenced commit that represents the result of merging two branches using a specified merge strategy. This can help you determine the outcome of a potential merge. This API cannot be used with the fast-forward merge strategy because that strategy does not create a merge commit.

      This unreferenced merge commit can only be accessed using the GetCommit API or through git commands such as git fetch. To retrieve this commit, you must specify its commit ID or otherwise reference it.


      This is a convenience which creates an instance of the CreateUnreferencedMergeCommitRequest.Builder avoiding the need to create one manually via CreateUnreferencedMergeCommitRequest.builder()

      Parameters:
      createUnreferencedMergeCommitRequest - A Consumer that will call methods on CreateUnreferencedMergeCommitRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateUnreferencedMergeCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteApprovalRuleTemplate

      default CompletableFuture<DeleteApprovalRuleTemplateResponse> deleteApprovalRuleTemplate(DeleteApprovalRuleTemplateRequest deleteApprovalRuleTemplateRequest)

      Deletes a specified approval rule template. Deleting a template does not remove approval rules on pull requests already created with the template.

      Parameters:
      deleteApprovalRuleTemplateRequest -
      Returns:
      A Java Future containing the result of the DeleteApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateInUseException The approval rule template is associated with one or more repositories. You cannot delete a template that is associated with a repository. Remove all associations, and then try again.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteApprovalRuleTemplate

      default CompletableFuture<DeleteApprovalRuleTemplateResponse> deleteApprovalRuleTemplate(Consumer<DeleteApprovalRuleTemplateRequest.Builder> deleteApprovalRuleTemplateRequest)

      Deletes a specified approval rule template. Deleting a template does not remove approval rules on pull requests already created with the template.


      This is a convenience which creates an instance of the DeleteApprovalRuleTemplateRequest.Builder avoiding the need to create one manually via DeleteApprovalRuleTemplateRequest.builder()

      Parameters:
      deleteApprovalRuleTemplateRequest - A Consumer that will call methods on DeleteApprovalRuleTemplateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateInUseException The approval rule template is associated with one or more repositories. You cannot delete a template that is associated with a repository. Remove all associations, and then try again.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteBranch

      default CompletableFuture<DeleteBranchResponse> deleteBranch(DeleteBranchRequest deleteBranchRequest)

      Deletes a branch from a repository, unless that branch is the default branch for the repository.

      Parameters:
      deleteBranchRequest - Represents the input of a delete branch operation.
      Returns:
      A Java Future containing the result of the DeleteBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • DefaultBranchCannotBeDeletedException The specified branch is the default branch for the repository, and cannot be deleted. To delete this branch, you must first set another branch as the default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteBranch

      default CompletableFuture<DeleteBranchResponse> deleteBranch(Consumer<DeleteBranchRequest.Builder> deleteBranchRequest)

      Deletes a branch from a repository, unless that branch is the default branch for the repository.


      This is a convenience which creates an instance of the DeleteBranchRequest.Builder avoiding the need to create one manually via DeleteBranchRequest.builder()

      Parameters:
      deleteBranchRequest - A Consumer that will call methods on DeleteBranchRequest.Builder to create a request. Represents the input of a delete branch operation.
      Returns:
      A Java Future containing the result of the DeleteBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • DefaultBranchCannotBeDeletedException The specified branch is the default branch for the repository, and cannot be deleted. To delete this branch, you must first set another branch as the default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteCommentContent

      default CompletableFuture<DeleteCommentContentResponse> deleteCommentContent(DeleteCommentContentRequest deleteCommentContentRequest)

      Deletes the content of a comment made on a change, file, or commit in a repository.

      Parameters:
      deleteCommentContentRequest -
      Returns:
      A Java Future containing the result of the DeleteCommentContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteCommentContent

      default CompletableFuture<DeleteCommentContentResponse> deleteCommentContent(Consumer<DeleteCommentContentRequest.Builder> deleteCommentContentRequest)

      Deletes the content of a comment made on a change, file, or commit in a repository.


      This is a convenience which creates an instance of the DeleteCommentContentRequest.Builder avoiding the need to create one manually via DeleteCommentContentRequest.builder()

      Parameters:
      deleteCommentContentRequest - A Consumer that will call methods on DeleteCommentContentRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteCommentContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteFile

      default CompletableFuture<DeleteFileResponse> deleteFile(DeleteFileRequest deleteFileRequest)

      Deletes a specified file from a specified branch. A commit is created on the branch that contains the revision. The file still exists in the commits earlier to the commit that contains the deletion.

      Parameters:
      deleteFileRequest -
      Returns:
      A Java Future containing the result of the DeleteFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteFile

      default CompletableFuture<DeleteFileResponse> deleteFile(Consumer<DeleteFileRequest.Builder> deleteFileRequest)

      Deletes a specified file from a specified branch. A commit is created on the branch that contains the revision. The file still exists in the commits earlier to the commit that contains the deletion.


      This is a convenience which creates an instance of the DeleteFileRequest.Builder avoiding the need to create one manually via DeleteFileRequest.builder()

      Parameters:
      deleteFileRequest - A Consumer that will call methods on DeleteFileRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deletePullRequestApprovalRule

      default CompletableFuture<DeletePullRequestApprovalRuleResponse> deletePullRequestApprovalRule(DeletePullRequestApprovalRuleRequest deletePullRequestApprovalRuleRequest)

      Deletes an approval rule from a specified pull request. Approval rules can be deleted from a pull request only if the pull request is open, and if the approval rule was created specifically for a pull request and not generated from an approval rule template associated with the repository where the pull request was created. You cannot delete an approval rule from a merged or closed pull request.

      Parameters:
      deletePullRequestApprovalRuleRequest -
      Returns:
      A Java Future containing the result of the DeletePullRequestApprovalRule operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • CannotDeleteApprovalRuleFromTemplateException The approval rule cannot be deleted from the pull request because it was created by an approval rule template and applied to the pull request automatically.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deletePullRequestApprovalRule

      default CompletableFuture<DeletePullRequestApprovalRuleResponse> deletePullRequestApprovalRule(Consumer<DeletePullRequestApprovalRuleRequest.Builder> deletePullRequestApprovalRuleRequest)

      Deletes an approval rule from a specified pull request. Approval rules can be deleted from a pull request only if the pull request is open, and if the approval rule was created specifically for a pull request and not generated from an approval rule template associated with the repository where the pull request was created. You cannot delete an approval rule from a merged or closed pull request.


      This is a convenience which creates an instance of the DeletePullRequestApprovalRuleRequest.Builder avoiding the need to create one manually via DeletePullRequestApprovalRuleRequest.builder()

      Parameters:
      deletePullRequestApprovalRuleRequest - A Consumer that will call methods on DeletePullRequestApprovalRuleRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeletePullRequestApprovalRule operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • CannotDeleteApprovalRuleFromTemplateException The approval rule cannot be deleted from the pull request because it was created by an approval rule template and applied to the pull request automatically.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteRepository

      default CompletableFuture<DeleteRepositoryResponse> deleteRepository(DeleteRepositoryRequest deleteRepositoryRequest)

      Deletes a repository. If a specified repository was already deleted, a null repository ID is returned.

      Deleting a repository also deletes all associated objects and metadata. After a repository is deleted, all future push calls to the deleted repository fail.

      Parameters:
      deleteRepositoryRequest - Represents the input of a delete repository operation.
      Returns:
      A Java Future containing the result of the DeleteRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteRepository

      default CompletableFuture<DeleteRepositoryResponse> deleteRepository(Consumer<DeleteRepositoryRequest.Builder> deleteRepositoryRequest)

      Deletes a repository. If a specified repository was already deleted, a null repository ID is returned.

      Deleting a repository also deletes all associated objects and metadata. After a repository is deleted, all future push calls to the deleted repository fail.


      This is a convenience which creates an instance of the DeleteRepositoryRequest.Builder avoiding the need to create one manually via DeleteRepositoryRequest.builder()

      Parameters:
      deleteRepositoryRequest - A Consumer that will call methods on DeleteRepositoryRequest.Builder to create a request. Represents the input of a delete repository operation.
      Returns:
      A Java Future containing the result of the DeleteRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeMergeConflicts

      default CompletableFuture<DescribeMergeConflictsResponse> describeMergeConflicts(DescribeMergeConflictsRequest describeMergeConflictsRequest)

      Returns information about one or more merge conflicts in the attempted merge of two commit specifiers using the squash or three-way merge strategy. If the merge option for the attempted merge is specified as FAST_FORWARD_MERGE, an exception is thrown.

      Parameters:
      describeMergeConflictsRequest -
      Returns:
      A Java Future containing the result of the DescribeMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeMergeConflicts

      default CompletableFuture<DescribeMergeConflictsResponse> describeMergeConflicts(Consumer<DescribeMergeConflictsRequest.Builder> describeMergeConflictsRequest)

      Returns information about one or more merge conflicts in the attempted merge of two commit specifiers using the squash or three-way merge strategy. If the merge option for the attempted merge is specified as FAST_FORWARD_MERGE, an exception is thrown.


      This is a convenience which creates an instance of the DescribeMergeConflictsRequest.Builder avoiding the need to create one manually via DescribeMergeConflictsRequest.builder()

      Parameters:
      describeMergeConflictsRequest - A Consumer that will call methods on DescribeMergeConflictsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeMergeConflictsPaginator

      default DescribeMergeConflictsPublisher describeMergeConflictsPaginator(DescribeMergeConflictsRequest describeMergeConflictsRequest)

      This is a variant of describeMergeConflicts(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxMergeHunks won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the describeMergeConflicts(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation.

      Parameters:
      describeMergeConflictsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeMergeConflictsPaginator

      default DescribeMergeConflictsPublisher describeMergeConflictsPaginator(Consumer<DescribeMergeConflictsRequest.Builder> describeMergeConflictsRequest)

      This is a variant of describeMergeConflicts(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxMergeHunks won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the describeMergeConflicts(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation.


      This is a convenience which creates an instance of the DescribeMergeConflictsRequest.Builder avoiding the need to create one manually via DescribeMergeConflictsRequest.builder()

      Parameters:
      describeMergeConflictsRequest - A Consumer that will call methods on DescribeMergeConflictsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • InvalidMaxMergeHunksException The specified value for the number of merge hunks to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePullRequestEvents

      default CompletableFuture<DescribePullRequestEventsResponse> describePullRequestEvents(DescribePullRequestEventsRequest describePullRequestEventsRequest)

      Returns information about one or more pull request events.

      Parameters:
      describePullRequestEventsRequest -
      Returns:
      A Java Future containing the result of the DescribePullRequestEvents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestEventTypeException The pull request event type is not valid.
      • InvalidActorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the user who initiated the change for the pull request, and then try again.
      • ActorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePullRequestEvents

      default CompletableFuture<DescribePullRequestEventsResponse> describePullRequestEvents(Consumer<DescribePullRequestEventsRequest.Builder> describePullRequestEventsRequest)

      Returns information about one or more pull request events.


      This is a convenience which creates an instance of the DescribePullRequestEventsRequest.Builder avoiding the need to create one manually via DescribePullRequestEventsRequest.builder()

      Parameters:
      describePullRequestEventsRequest - A Consumer that will call methods on DescribePullRequestEventsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribePullRequestEvents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestEventTypeException The pull request event type is not valid.
      • InvalidActorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the user who initiated the change for the pull request, and then try again.
      • ActorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePullRequestEventsPaginator

      default DescribePullRequestEventsPublisher describePullRequestEventsPaginator(DescribePullRequestEventsRequest describePullRequestEventsRequest)

      This is a variant of describePullRequestEvents(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribePullRequestEventsPublisher publisher = client.describePullRequestEventsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribePullRequestEventsPublisher publisher = client.describePullRequestEventsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the describePullRequestEvents(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsRequest) operation.

      Parameters:
      describePullRequestEventsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestEventTypeException The pull request event type is not valid.
      • InvalidActorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the user who initiated the change for the pull request, and then try again.
      • ActorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePullRequestEventsPaginator

      default DescribePullRequestEventsPublisher describePullRequestEventsPaginator(Consumer<DescribePullRequestEventsRequest.Builder> describePullRequestEventsRequest)

      This is a variant of describePullRequestEvents(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribePullRequestEventsPublisher publisher = client.describePullRequestEventsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.DescribePullRequestEventsPublisher publisher = client.describePullRequestEventsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the describePullRequestEvents(software.amazon.awssdk.services.codecommit.model.DescribePullRequestEventsRequest) operation.


      This is a convenience which creates an instance of the DescribePullRequestEventsRequest.Builder avoiding the need to create one manually via DescribePullRequestEventsRequest.builder()

      Parameters:
      describePullRequestEventsRequest - A Consumer that will call methods on DescribePullRequestEventsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestEventTypeException The pull request event type is not valid.
      • InvalidActorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the user who initiated the change for the pull request, and then try again.
      • ActorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • disassociateApprovalRuleTemplateFromRepository

      default CompletableFuture<DisassociateApprovalRuleTemplateFromRepositoryResponse> disassociateApprovalRuleTemplateFromRepository(DisassociateApprovalRuleTemplateFromRepositoryRequest disassociateApprovalRuleTemplateFromRepositoryRequest)

      Removes the association between a template and a repository so that approval rules based on the template are not automatically created when pull requests are created in the specified repository. This does not delete any approval rules previously created for pull requests through the template association.

      Parameters:
      disassociateApprovalRuleTemplateFromRepositoryRequest -
      Returns:
      A Java Future containing the result of the DisassociateApprovalRuleTemplateFromRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • disassociateApprovalRuleTemplateFromRepository

      default CompletableFuture<DisassociateApprovalRuleTemplateFromRepositoryResponse> disassociateApprovalRuleTemplateFromRepository(Consumer<DisassociateApprovalRuleTemplateFromRepositoryRequest.Builder> disassociateApprovalRuleTemplateFromRepositoryRequest)

      Removes the association between a template and a repository so that approval rules based on the template are not automatically created when pull requests are created in the specified repository. This does not delete any approval rules previously created for pull requests through the template association.


      This is a convenience which creates an instance of the DisassociateApprovalRuleTemplateFromRepositoryRequest.Builder avoiding the need to create one manually via DisassociateApprovalRuleTemplateFromRepositoryRequest.builder()

      Parameters:
      disassociateApprovalRuleTemplateFromRepositoryRequest - A Consumer that will call methods on DisassociateApprovalRuleTemplateFromRepositoryRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DisassociateApprovalRuleTemplateFromRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • evaluatePullRequestApprovalRules

      default CompletableFuture<EvaluatePullRequestApprovalRulesResponse> evaluatePullRequestApprovalRules(EvaluatePullRequestApprovalRulesRequest evaluatePullRequestApprovalRulesRequest)

      Evaluates whether a pull request has met all the conditions specified in its associated approval rules.

      Parameters:
      evaluatePullRequestApprovalRulesRequest -
      Returns:
      A Java Future containing the result of the EvaluatePullRequestApprovalRules operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • evaluatePullRequestApprovalRules

      default CompletableFuture<EvaluatePullRequestApprovalRulesResponse> evaluatePullRequestApprovalRules(Consumer<EvaluatePullRequestApprovalRulesRequest.Builder> evaluatePullRequestApprovalRulesRequest)

      Evaluates whether a pull request has met all the conditions specified in its associated approval rules.


      This is a convenience which creates an instance of the EvaluatePullRequestApprovalRulesRequest.Builder avoiding the need to create one manually via EvaluatePullRequestApprovalRulesRequest.builder()

      Parameters:
      evaluatePullRequestApprovalRulesRequest - A Consumer that will call methods on EvaluatePullRequestApprovalRulesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the EvaluatePullRequestApprovalRules operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getApprovalRuleTemplate

      default CompletableFuture<GetApprovalRuleTemplateResponse> getApprovalRuleTemplate(GetApprovalRuleTemplateRequest getApprovalRuleTemplateRequest)

      Returns information about a specified approval rule template.

      Parameters:
      getApprovalRuleTemplateRequest -
      Returns:
      A Java Future containing the result of the GetApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getApprovalRuleTemplate

      default CompletableFuture<GetApprovalRuleTemplateResponse> getApprovalRuleTemplate(Consumer<GetApprovalRuleTemplateRequest.Builder> getApprovalRuleTemplateRequest)

      Returns information about a specified approval rule template.


      This is a convenience which creates an instance of the GetApprovalRuleTemplateRequest.Builder avoiding the need to create one manually via GetApprovalRuleTemplateRequest.builder()

      Parameters:
      getApprovalRuleTemplateRequest - A Consumer that will call methods on GetApprovalRuleTemplateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getBlob

      default CompletableFuture<GetBlobResponse> getBlob(GetBlobRequest getBlobRequest)

      Returns the base-64 encoded content of an individual blob in a repository.

      Parameters:
      getBlobRequest - Represents the input of a get blob operation.
      Returns:
      A Java Future containing the result of the GetBlob operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • BlobIdRequiredException A blob ID is required, but was not specified.
      • InvalidBlobIdException The specified blob is not valid.
      • BlobIdDoesNotExistException The specified blob does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • FileTooLargeException The specified file exceeds the file size limit for CodeCommit. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getBlob

      default CompletableFuture<GetBlobResponse> getBlob(Consumer<GetBlobRequest.Builder> getBlobRequest)

      Returns the base-64 encoded content of an individual blob in a repository.


      This is a convenience which creates an instance of the GetBlobRequest.Builder avoiding the need to create one manually via GetBlobRequest.builder()

      Parameters:
      getBlobRequest - A Consumer that will call methods on GetBlobRequest.Builder to create a request. Represents the input of a get blob operation.
      Returns:
      A Java Future containing the result of the GetBlob operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • BlobIdRequiredException A blob ID is required, but was not specified.
      • InvalidBlobIdException The specified blob is not valid.
      • BlobIdDoesNotExistException The specified blob does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • FileTooLargeException The specified file exceeds the file size limit for CodeCommit. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getBranch

      default CompletableFuture<GetBranchResponse> getBranch(GetBranchRequest getBranchRequest)

      Returns information about a repository branch, including its name and the last commit ID.

      Parameters:
      getBranchRequest - Represents the input of a get branch operation.
      Returns:
      A Java Future containing the result of the GetBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getBranch

      default CompletableFuture<GetBranchResponse> getBranch(Consumer<GetBranchRequest.Builder> getBranchRequest)

      Returns information about a repository branch, including its name and the last commit ID.


      This is a convenience which creates an instance of the GetBranchRequest.Builder avoiding the need to create one manually via GetBranchRequest.builder()

      Parameters:
      getBranchRequest - A Consumer that will call methods on GetBranchRequest.Builder to create a request. Represents the input of a get branch operation.
      Returns:
      A Java Future containing the result of the GetBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getComment

      default CompletableFuture<GetCommentResponse> getComment(GetCommentRequest getCommentRequest)

      Returns the content of a comment made on a change, file, or commit in a repository.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.

      Parameters:
      getCommentRequest -
      Returns:
      A Java Future containing the result of the GetComment operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getComment

      default CompletableFuture<GetCommentResponse> getComment(Consumer<GetCommentRequest.Builder> getCommentRequest)

      Returns the content of a comment made on a change, file, or commit in a repository.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.


      This is a convenience which creates an instance of the GetCommentRequest.Builder avoiding the need to create one manually via GetCommentRequest.builder()

      Parameters:
      getCommentRequest - A Consumer that will call methods on GetCommentRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetComment operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentReactions

      default CompletableFuture<GetCommentReactionsResponse> getCommentReactions(GetCommentReactionsRequest getCommentReactionsRequest)

      Returns information about reactions to a specified comment ID. Reactions from users who have been deleted will not be included in the count.

      Parameters:
      getCommentReactionsRequest -
      Returns:
      A Java Future containing the result of the GetCommentReactions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionUserArnException The Amazon Resource Name (ARN) of the user or identity is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentReactions

      default CompletableFuture<GetCommentReactionsResponse> getCommentReactions(Consumer<GetCommentReactionsRequest.Builder> getCommentReactionsRequest)

      Returns information about reactions to a specified comment ID. Reactions from users who have been deleted will not be included in the count.


      This is a convenience which creates an instance of the GetCommentReactionsRequest.Builder avoiding the need to create one manually via GetCommentReactionsRequest.builder()

      Parameters:
      getCommentReactionsRequest - A Consumer that will call methods on GetCommentReactionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetCommentReactions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionUserArnException The Amazon Resource Name (ARN) of the user or identity is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentReactionsPaginator

      default GetCommentReactionsPublisher getCommentReactionsPaginator(GetCommentReactionsRequest getCommentReactionsRequest)

      This is a variant of getCommentReactions(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentReactionsPublisher publisher = client.getCommentReactionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentReactionsPublisher publisher = client.getCommentReactionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentReactionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentReactions(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsRequest) operation.

      Parameters:
      getCommentReactionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionUserArnException The Amazon Resource Name (ARN) of the user or identity is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentReactionsPaginator

      default GetCommentReactionsPublisher getCommentReactionsPaginator(Consumer<GetCommentReactionsRequest.Builder> getCommentReactionsRequest)

      This is a variant of getCommentReactions(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentReactionsPublisher publisher = client.getCommentReactionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentReactionsPublisher publisher = client.getCommentReactionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentReactionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentReactions(software.amazon.awssdk.services.codecommit.model.GetCommentReactionsRequest) operation.


      This is a convenience which creates an instance of the GetCommentReactionsRequest.Builder avoiding the need to create one manually via GetCommentReactionsRequest.builder()

      Parameters:
      getCommentReactionsRequest - A Consumer that will call methods on GetCommentReactionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionUserArnException The Amazon Resource Name (ARN) of the user or identity is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForComparedCommit

      default CompletableFuture<GetCommentsForComparedCommitResponse> getCommentsForComparedCommit(GetCommentsForComparedCommitRequest getCommentsForComparedCommitRequest)

      Returns information about comments made on the comparison between two commits.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.

      Parameters:
      getCommentsForComparedCommitRequest -
      Returns:
      A Java Future containing the result of the GetCommentsForComparedCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForComparedCommit

      default CompletableFuture<GetCommentsForComparedCommitResponse> getCommentsForComparedCommit(Consumer<GetCommentsForComparedCommitRequest.Builder> getCommentsForComparedCommitRequest)

      Returns information about comments made on the comparison between two commits.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.


      This is a convenience which creates an instance of the GetCommentsForComparedCommitRequest.Builder avoiding the need to create one manually via GetCommentsForComparedCommitRequest.builder()

      Parameters:
      getCommentsForComparedCommitRequest - A Consumer that will call methods on GetCommentsForComparedCommitRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetCommentsForComparedCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForComparedCommitPaginator

      default GetCommentsForComparedCommitPublisher getCommentsForComparedCommitPaginator(GetCommentsForComparedCommitRequest getCommentsForComparedCommitRequest)

      This is a variant of getCommentsForComparedCommit(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForComparedCommitPublisher publisher = client.getCommentsForComparedCommitPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForComparedCommitPublisher publisher = client.getCommentsForComparedCommitPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentsForComparedCommit(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitRequest) operation.

      Parameters:
      getCommentsForComparedCommitRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForComparedCommitPaginator

      default GetCommentsForComparedCommitPublisher getCommentsForComparedCommitPaginator(Consumer<GetCommentsForComparedCommitRequest.Builder> getCommentsForComparedCommitRequest)

      This is a variant of getCommentsForComparedCommit(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForComparedCommitPublisher publisher = client.getCommentsForComparedCommitPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForComparedCommitPublisher publisher = client.getCommentsForComparedCommitPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentsForComparedCommit(software.amazon.awssdk.services.codecommit.model.GetCommentsForComparedCommitRequest) operation.


      This is a convenience which creates an instance of the GetCommentsForComparedCommitRequest.Builder avoiding the need to create one manually via GetCommentsForComparedCommitRequest.builder()

      Parameters:
      getCommentsForComparedCommitRequest - A Consumer that will call methods on GetCommentsForComparedCommitRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForPullRequest

      default CompletableFuture<GetCommentsForPullRequestResponse> getCommentsForPullRequest(GetCommentsForPullRequestRequest getCommentsForPullRequestRequest)

      Returns comments made on a pull request.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.

      Parameters:
      getCommentsForPullRequestRequest -
      Returns:
      A Java Future containing the result of the GetCommentsForPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForPullRequest

      default CompletableFuture<GetCommentsForPullRequestResponse> getCommentsForPullRequest(Consumer<GetCommentsForPullRequestRequest.Builder> getCommentsForPullRequestRequest)

      Returns comments made on a pull request.

      Reaction counts might include numbers from user identities who were deleted after the reaction was made. For a count of reactions from active identities, use GetCommentReactions.


      This is a convenience which creates an instance of the GetCommentsForPullRequestRequest.Builder avoiding the need to create one manually via GetCommentsForPullRequestRequest.builder()

      Parameters:
      getCommentsForPullRequestRequest - A Consumer that will call methods on GetCommentsForPullRequestRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetCommentsForPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForPullRequestPaginator

      default GetCommentsForPullRequestPublisher getCommentsForPullRequestPaginator(GetCommentsForPullRequestRequest getCommentsForPullRequestRequest)

      This is a variant of getCommentsForPullRequest(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForPullRequestPublisher publisher = client.getCommentsForPullRequestPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForPullRequestPublisher publisher = client.getCommentsForPullRequestPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentsForPullRequest(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestRequest) operation.

      Parameters:
      getCommentsForPullRequestRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommentsForPullRequestPaginator

      default GetCommentsForPullRequestPublisher getCommentsForPullRequestPaginator(Consumer<GetCommentsForPullRequestRequest.Builder> getCommentsForPullRequestRequest)

      This is a variant of getCommentsForPullRequest(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForPullRequestPublisher publisher = client.getCommentsForPullRequestPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetCommentsForPullRequestPublisher publisher = client.getCommentsForPullRequestPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getCommentsForPullRequest(software.amazon.awssdk.services.codecommit.model.GetCommentsForPullRequestRequest) operation.


      This is a convenience which creates an instance of the GetCommentsForPullRequestRequest.Builder avoiding the need to create one manually via GetCommentsForPullRequestRequest.builder()

      Parameters:
      getCommentsForPullRequestRequest - A Consumer that will call methods on GetCommentsForPullRequestRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommit

      default CompletableFuture<GetCommitResponse> getCommit(GetCommitRequest getCommitRequest)

      Returns information about a commit, including commit message and committer information.

      Parameters:
      getCommitRequest - Represents the input of a get commit operation.
      Returns:
      A Java Future containing the result of the GetCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitIdDoesNotExistException The specified commit ID does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getCommit

      default CompletableFuture<GetCommitResponse> getCommit(Consumer<GetCommitRequest.Builder> getCommitRequest)

      Returns information about a commit, including commit message and committer information.


      This is a convenience which creates an instance of the GetCommitRequest.Builder avoiding the need to create one manually via GetCommitRequest.builder()

      Parameters:
      getCommitRequest - A Consumer that will call methods on GetCommitRequest.Builder to create a request. Represents the input of a get commit operation.
      Returns:
      A Java Future containing the result of the GetCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitIdDoesNotExistException The specified commit ID does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDifferences

      default CompletableFuture<GetDifferencesResponse> getDifferences(GetDifferencesRequest getDifferencesRequest)

      Returns information about the differences in a valid commit specifier (such as a branch, tag, HEAD, commit ID, or other fully qualified reference). Results can be limited to a specified path.

      Parameters:
      getDifferencesRequest -
      Returns:
      A Java Future containing the result of the GetDifferences operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDifferences

      default CompletableFuture<GetDifferencesResponse> getDifferences(Consumer<GetDifferencesRequest.Builder> getDifferencesRequest)

      Returns information about the differences in a valid commit specifier (such as a branch, tag, HEAD, commit ID, or other fully qualified reference). Results can be limited to a specified path.


      This is a convenience which creates an instance of the GetDifferencesRequest.Builder avoiding the need to create one manually via GetDifferencesRequest.builder()

      Parameters:
      getDifferencesRequest - A Consumer that will call methods on GetDifferencesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetDifferences operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDifferencesPaginator

      default GetDifferencesPublisher getDifferencesPaginator(GetDifferencesRequest getDifferencesRequest)

      This is a variant of getDifferences(software.amazon.awssdk.services.codecommit.model.GetDifferencesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetDifferencesPublisher publisher = client.getDifferencesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetDifferencesPublisher publisher = client.getDifferencesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetDifferencesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetDifferencesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getDifferences(software.amazon.awssdk.services.codecommit.model.GetDifferencesRequest) operation.

      Parameters:
      getDifferencesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getDifferencesPaginator

      default GetDifferencesPublisher getDifferencesPaginator(Consumer<GetDifferencesRequest.Builder> getDifferencesRequest)

      This is a variant of getDifferences(software.amazon.awssdk.services.codecommit.model.GetDifferencesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetDifferencesPublisher publisher = client.getDifferencesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetDifferencesPublisher publisher = client.getDifferencesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetDifferencesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetDifferencesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of MaxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getDifferences(software.amazon.awssdk.services.codecommit.model.GetDifferencesRequest) operation.


      This is a convenience which creates an instance of the GetDifferencesRequest.Builder avoiding the need to create one manually via GetDifferencesRequest.builder()

      Parameters:
      getDifferencesRequest - A Consumer that will call methods on GetDifferencesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidCommitIdException The specified commit ID is not valid.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getFile

      default CompletableFuture<GetFileResponse> getFile(GetFileRequest getFileRequest)

      Returns the base-64 encoded contents of a specified file and its metadata.

      Parameters:
      getFileRequest -
      Returns:
      A Java Future containing the result of the GetFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • FileTooLargeException The specified file exceeds the file size limit for CodeCommit. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getFile

      default CompletableFuture<GetFileResponse> getFile(Consumer<GetFileRequest.Builder> getFileRequest)

      Returns the base-64 encoded contents of a specified file and its metadata.


      This is a convenience which creates an instance of the GetFileRequest.Builder avoiding the need to create one manually via GetFileRequest.builder()

      Parameters:
      getFileRequest - A Consumer that will call methods on GetFileRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileDoesNotExistException The specified file does not exist. Verify that you have used the correct file name, full path, and extension.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • FileTooLargeException The specified file exceeds the file size limit for CodeCommit. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getFolder

      default CompletableFuture<GetFolderResponse> getFolder(GetFolderRequest getFolderRequest)

      Returns the contents of a specified folder in a repository.

      Parameters:
      getFolderRequest -
      Returns:
      A Java Future containing the result of the GetFolder operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FolderDoesNotExistException The specified folder does not exist. Either the folder name is not correct, or you did not enter the full path to the folder.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getFolder

      default CompletableFuture<GetFolderResponse> getFolder(Consumer<GetFolderRequest.Builder> getFolderRequest)

      Returns the contents of a specified folder in a repository.


      This is a convenience which creates an instance of the GetFolderRequest.Builder avoiding the need to create one manually via GetFolderRequest.builder()

      Parameters:
      getFolderRequest - A Consumer that will call methods on GetFolderRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetFolder operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FolderDoesNotExistException The specified folder does not exist. Either the folder name is not correct, or you did not enter the full path to the folder.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeCommit

      default CompletableFuture<GetMergeCommitResponse> getMergeCommit(GetMergeCommitRequest getMergeCommitRequest)

      Returns information about a specified merge commit.

      Parameters:
      getMergeCommitRequest -
      Returns:
      A Java Future containing the result of the GetMergeCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeCommit

      default CompletableFuture<GetMergeCommitResponse> getMergeCommit(Consumer<GetMergeCommitRequest.Builder> getMergeCommitRequest)

      Returns information about a specified merge commit.


      This is a convenience which creates an instance of the GetMergeCommitRequest.Builder avoiding the need to create one manually via GetMergeCommitRequest.builder()

      Parameters:
      getMergeCommitRequest - A Consumer that will call methods on GetMergeCommitRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetMergeCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeConflicts

      default CompletableFuture<GetMergeConflictsResponse> getMergeConflicts(GetMergeConflictsRequest getMergeConflictsRequest)

      Returns information about merge conflicts between the before and after commit IDs for a pull request in a repository.

      Parameters:
      getMergeConflictsRequest -
      Returns:
      A Java Future containing the result of the GetMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidDestinationCommitSpecifierException The destination commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidSourceCommitSpecifierException The source commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeConflicts

      default CompletableFuture<GetMergeConflictsResponse> getMergeConflicts(Consumer<GetMergeConflictsRequest.Builder> getMergeConflictsRequest)

      Returns information about merge conflicts between the before and after commit IDs for a pull request in a repository.


      This is a convenience which creates an instance of the GetMergeConflictsRequest.Builder avoiding the need to create one manually via GetMergeConflictsRequest.builder()

      Parameters:
      getMergeConflictsRequest - A Consumer that will call methods on GetMergeConflictsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetMergeConflicts operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidDestinationCommitSpecifierException The destination commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidSourceCommitSpecifierException The source commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeConflictsPaginator

      default GetMergeConflictsPublisher getMergeConflictsPaginator(GetMergeConflictsRequest getMergeConflictsRequest)

      This is a variant of getMergeConflicts(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetMergeConflictsPublisher publisher = client.getMergeConflictsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetMergeConflictsPublisher publisher = client.getMergeConflictsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetMergeConflictsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxConflictFiles won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getMergeConflicts(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsRequest) operation.

      Parameters:
      getMergeConflictsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidDestinationCommitSpecifierException The destination commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidSourceCommitSpecifierException The source commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeConflictsPaginator

      default GetMergeConflictsPublisher getMergeConflictsPaginator(Consumer<GetMergeConflictsRequest.Builder> getMergeConflictsRequest)

      This is a variant of getMergeConflicts(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.GetMergeConflictsPublisher publisher = client.getMergeConflictsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.GetMergeConflictsPublisher publisher = client.getMergeConflictsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.GetMergeConflictsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxConflictFiles won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the getMergeConflicts(software.amazon.awssdk.services.codecommit.model.GetMergeConflictsRequest) operation.


      This is a convenience which creates an instance of the GetMergeConflictsRequest.Builder avoiding the need to create one manually via GetMergeConflictsRequest.builder()

      Parameters:
      getMergeConflictsRequest - A Consumer that will call methods on GetMergeConflictsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • MergeOptionRequiredException A merge option or stategy is required, and none was provided.
      • InvalidMergeOptionException The specified merge option is not valid for this operation. Not all merge strategies are supported for all operations.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidMaxConflictFilesException The specified value for the number of conflict files to return is not valid.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidDestinationCommitSpecifierException The destination commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidSourceCommitSpecifierException The source commit specifier is not valid. You must provide a valid branch name, tag, or full commit ID.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeOptions

      default CompletableFuture<GetMergeOptionsResponse> getMergeOptions(GetMergeOptionsRequest getMergeOptionsRequest)

      Returns information about the merge options available for merging two specified branches. For details about why a merge option is not available, use GetMergeConflicts or DescribeMergeConflicts.

      Parameters:
      getMergeOptionsRequest -
      Returns:
      A Java Future containing the result of the GetMergeOptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getMergeOptions

      default CompletableFuture<GetMergeOptionsResponse> getMergeOptions(Consumer<GetMergeOptionsRequest.Builder> getMergeOptionsRequest)

      Returns information about the merge options available for merging two specified branches. For details about why a merge option is not available, use GetMergeConflicts or DescribeMergeConflicts.


      This is a convenience which creates an instance of the GetMergeOptionsRequest.Builder avoiding the need to create one manually via GetMergeOptionsRequest.builder()

      Parameters:
      getMergeOptionsRequest - A Consumer that will call methods on GetMergeOptionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetMergeOptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • CommitRequiredException A commit was not specified.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidCommitException The specified commit is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequest

      default CompletableFuture<GetPullRequestResponse> getPullRequest(GetPullRequestRequest getPullRequestRequest)

      Gets information about a pull request in a specified repository.

      Parameters:
      getPullRequestRequest -
      Returns:
      A Java Future containing the result of the GetPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequest

      default CompletableFuture<GetPullRequestResponse> getPullRequest(Consumer<GetPullRequestRequest.Builder> getPullRequestRequest)

      Gets information about a pull request in a specified repository.


      This is a convenience which creates an instance of the GetPullRequestRequest.Builder avoiding the need to create one manually via GetPullRequestRequest.builder()

      Parameters:
      getPullRequestRequest - A Consumer that will call methods on GetPullRequestRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequestApprovalStates

      default CompletableFuture<GetPullRequestApprovalStatesResponse> getPullRequestApprovalStates(GetPullRequestApprovalStatesRequest getPullRequestApprovalStatesRequest)

      Gets information about the approval states for a specified pull request. Approval states only apply to pull requests that have one or more approval rules applied to them.

      Parameters:
      getPullRequestApprovalStatesRequest -
      Returns:
      A Java Future containing the result of the GetPullRequestApprovalStates operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequestApprovalStates

      default CompletableFuture<GetPullRequestApprovalStatesResponse> getPullRequestApprovalStates(Consumer<GetPullRequestApprovalStatesRequest.Builder> getPullRequestApprovalStatesRequest)

      Gets information about the approval states for a specified pull request. Approval states only apply to pull requests that have one or more approval rules applied to them.


      This is a convenience which creates an instance of the GetPullRequestApprovalStatesRequest.Builder avoiding the need to create one manually via GetPullRequestApprovalStatesRequest.builder()

      Parameters:
      getPullRequestApprovalStatesRequest - A Consumer that will call methods on GetPullRequestApprovalStatesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetPullRequestApprovalStates operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequestOverrideState

      default CompletableFuture<GetPullRequestOverrideStateResponse> getPullRequestOverrideState(GetPullRequestOverrideStateRequest getPullRequestOverrideStateRequest)

      Returns information about whether approval rules have been set aside (overridden) for a pull request, and if so, the Amazon Resource Name (ARN) of the user or identity that overrode the rules and their requirements for the pull request.

      Parameters:
      getPullRequestOverrideStateRequest -
      Returns:
      A Java Future containing the result of the GetPullRequestOverrideState operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getPullRequestOverrideState

      default CompletableFuture<GetPullRequestOverrideStateResponse> getPullRequestOverrideState(Consumer<GetPullRequestOverrideStateRequest.Builder> getPullRequestOverrideStateRequest)

      Returns information about whether approval rules have been set aside (overridden) for a pull request, and if so, the Amazon Resource Name (ARN) of the user or identity that overrode the rules and their requirements for the pull request.


      This is a convenience which creates an instance of the GetPullRequestOverrideStateRequest.Builder avoiding the need to create one manually via GetPullRequestOverrideStateRequest.builder()

      Parameters:
      getPullRequestOverrideStateRequest - A Consumer that will call methods on GetPullRequestOverrideStateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the GetPullRequestOverrideState operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getRepository

      default CompletableFuture<GetRepositoryResponse> getRepository(GetRepositoryRequest getRepositoryRequest)

      Returns information about a repository.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.

      Parameters:
      getRepositoryRequest - Represents the input of a get repository operation.
      Returns:
      A Java Future containing the result of the GetRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getRepository

      default CompletableFuture<GetRepositoryResponse> getRepository(Consumer<GetRepositoryRequest.Builder> getRepositoryRequest)

      Returns information about a repository.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.


      This is a convenience which creates an instance of the GetRepositoryRequest.Builder avoiding the need to create one manually via GetRepositoryRequest.builder()

      Parameters:
      getRepositoryRequest - A Consumer that will call methods on GetRepositoryRequest.Builder to create a request. Represents the input of a get repository operation.
      Returns:
      A Java Future containing the result of the GetRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getRepositoryTriggers

      default CompletableFuture<GetRepositoryTriggersResponse> getRepositoryTriggers(GetRepositoryTriggersRequest getRepositoryTriggersRequest)

      Gets information about triggers configured for a repository.

      Parameters:
      getRepositoryTriggersRequest - Represents the input of a get repository triggers operation.
      Returns:
      A Java Future containing the result of the GetRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • getRepositoryTriggers

      default CompletableFuture<GetRepositoryTriggersResponse> getRepositoryTriggers(Consumer<GetRepositoryTriggersRequest.Builder> getRepositoryTriggersRequest)

      Gets information about triggers configured for a repository.


      This is a convenience which creates an instance of the GetRepositoryTriggersRequest.Builder avoiding the need to create one manually via GetRepositoryTriggersRequest.builder()

      Parameters:
      getRepositoryTriggersRequest - A Consumer that will call methods on GetRepositoryTriggersRequest.Builder to create a request. Represents the input of a get repository triggers operation.
      Returns:
      A Java Future containing the result of the GetRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listApprovalRuleTemplates

      default CompletableFuture<ListApprovalRuleTemplatesResponse> listApprovalRuleTemplates(ListApprovalRuleTemplatesRequest listApprovalRuleTemplatesRequest)

      Lists all approval rule templates in the specified Amazon Web Services Region in your Amazon Web Services account. If an Amazon Web Services Region is not specified, the Amazon Web Services Region where you are signed in is used.

      Parameters:
      listApprovalRuleTemplatesRequest -
      Returns:
      A Java Future containing the result of the ListApprovalRuleTemplates operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listApprovalRuleTemplates

      default CompletableFuture<ListApprovalRuleTemplatesResponse> listApprovalRuleTemplates(Consumer<ListApprovalRuleTemplatesRequest.Builder> listApprovalRuleTemplatesRequest)

      Lists all approval rule templates in the specified Amazon Web Services Region in your Amazon Web Services account. If an Amazon Web Services Region is not specified, the Amazon Web Services Region where you are signed in is used.


      This is a convenience which creates an instance of the ListApprovalRuleTemplatesRequest.Builder avoiding the need to create one manually via ListApprovalRuleTemplatesRequest.builder()

      Parameters:
      listApprovalRuleTemplatesRequest - A Consumer that will call methods on ListApprovalRuleTemplatesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListApprovalRuleTemplates operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listApprovalRuleTemplatesPaginator

      default ListApprovalRuleTemplatesPublisher listApprovalRuleTemplatesPaginator(ListApprovalRuleTemplatesRequest listApprovalRuleTemplatesRequest)

      This is a variant of listApprovalRuleTemplates(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListApprovalRuleTemplatesPublisher publisher = client.listApprovalRuleTemplatesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListApprovalRuleTemplatesPublisher publisher = client.listApprovalRuleTemplatesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listApprovalRuleTemplates(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesRequest) operation.

      Parameters:
      listApprovalRuleTemplatesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listApprovalRuleTemplatesPaginator

      default ListApprovalRuleTemplatesPublisher listApprovalRuleTemplatesPaginator(Consumer<ListApprovalRuleTemplatesRequest.Builder> listApprovalRuleTemplatesRequest)

      This is a variant of listApprovalRuleTemplates(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListApprovalRuleTemplatesPublisher publisher = client.listApprovalRuleTemplatesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListApprovalRuleTemplatesPublisher publisher = client.listApprovalRuleTemplatesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listApprovalRuleTemplates(software.amazon.awssdk.services.codecommit.model.ListApprovalRuleTemplatesRequest) operation.


      This is a convenience which creates an instance of the ListApprovalRuleTemplatesRequest.Builder avoiding the need to create one manually via ListApprovalRuleTemplatesRequest.builder()

      Parameters:
      listApprovalRuleTemplatesRequest - A Consumer that will call methods on ListApprovalRuleTemplatesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listAssociatedApprovalRuleTemplatesForRepository

      default CompletableFuture<ListAssociatedApprovalRuleTemplatesForRepositoryResponse> listAssociatedApprovalRuleTemplatesForRepository(ListAssociatedApprovalRuleTemplatesForRepositoryRequest listAssociatedApprovalRuleTemplatesForRepositoryRequest)

      Lists all approval rule templates that are associated with a specified repository.

      Parameters:
      listAssociatedApprovalRuleTemplatesForRepositoryRequest -
      Returns:
      A Java Future containing the result of the ListAssociatedApprovalRuleTemplatesForRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listAssociatedApprovalRuleTemplatesForRepository

      default CompletableFuture<ListAssociatedApprovalRuleTemplatesForRepositoryResponse> listAssociatedApprovalRuleTemplatesForRepository(Consumer<ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder> listAssociatedApprovalRuleTemplatesForRepositoryRequest)

      Lists all approval rule templates that are associated with a specified repository.


      This is a convenience which creates an instance of the ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder avoiding the need to create one manually via ListAssociatedApprovalRuleTemplatesForRepositoryRequest.builder()

      Parameters:
      listAssociatedApprovalRuleTemplatesForRepositoryRequest - A Consumer that will call methods on ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListAssociatedApprovalRuleTemplatesForRepository operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listAssociatedApprovalRuleTemplatesForRepositoryPaginator

      default ListAssociatedApprovalRuleTemplatesForRepositoryPublisher listAssociatedApprovalRuleTemplatesForRepositoryPaginator(ListAssociatedApprovalRuleTemplatesForRepositoryRequest listAssociatedApprovalRuleTemplatesForRepositoryRequest)

      This is a variant of listAssociatedApprovalRuleTemplatesForRepository(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListAssociatedApprovalRuleTemplatesForRepositoryPublisher publisher = client.listAssociatedApprovalRuleTemplatesForRepositoryPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListAssociatedApprovalRuleTemplatesForRepositoryPublisher publisher = client.listAssociatedApprovalRuleTemplatesForRepositoryPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listAssociatedApprovalRuleTemplatesForRepository(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryRequest) operation.

      Parameters:
      listAssociatedApprovalRuleTemplatesForRepositoryRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listAssociatedApprovalRuleTemplatesForRepositoryPaginator

      default ListAssociatedApprovalRuleTemplatesForRepositoryPublisher listAssociatedApprovalRuleTemplatesForRepositoryPaginator(Consumer<ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder> listAssociatedApprovalRuleTemplatesForRepositoryRequest)

      This is a variant of listAssociatedApprovalRuleTemplatesForRepository(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListAssociatedApprovalRuleTemplatesForRepositoryPublisher publisher = client.listAssociatedApprovalRuleTemplatesForRepositoryPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListAssociatedApprovalRuleTemplatesForRepositoryPublisher publisher = client.listAssociatedApprovalRuleTemplatesForRepositoryPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listAssociatedApprovalRuleTemplatesForRepository(software.amazon.awssdk.services.codecommit.model.ListAssociatedApprovalRuleTemplatesForRepositoryRequest) operation.


      This is a convenience which creates an instance of the ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder avoiding the need to create one manually via ListAssociatedApprovalRuleTemplatesForRepositoryRequest.builder()

      Parameters:
      listAssociatedApprovalRuleTemplatesForRepositoryRequest - A Consumer that will call methods on ListAssociatedApprovalRuleTemplatesForRepositoryRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listBranches

      default CompletableFuture<ListBranchesResponse> listBranches(ListBranchesRequest listBranchesRequest)

      Gets information about one or more branches in a repository.

      Parameters:
      listBranchesRequest - Represents the input of a list branches operation.
      Returns:
      A Java Future containing the result of the ListBranches operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listBranches

      default CompletableFuture<ListBranchesResponse> listBranches(Consumer<ListBranchesRequest.Builder> listBranchesRequest)

      Gets information about one or more branches in a repository.


      This is a convenience which creates an instance of the ListBranchesRequest.Builder avoiding the need to create one manually via ListBranchesRequest.builder()

      Parameters:
      listBranchesRequest - A Consumer that will call methods on ListBranchesRequest.Builder to create a request. Represents the input of a list branches operation.
      Returns:
      A Java Future containing the result of the ListBranches operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listBranchesPaginator

      default ListBranchesPublisher listBranchesPaginator(ListBranchesRequest listBranchesRequest)

      This is a variant of listBranches(software.amazon.awssdk.services.codecommit.model.ListBranchesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListBranchesPublisher publisher = client.listBranchesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListBranchesPublisher publisher = client.listBranchesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListBranchesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListBranchesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of null won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listBranches(software.amazon.awssdk.services.codecommit.model.ListBranchesRequest) operation.

      Parameters:
      listBranchesRequest - Represents the input of a list branches operation.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listBranchesPaginator

      default ListBranchesPublisher listBranchesPaginator(Consumer<ListBranchesRequest.Builder> listBranchesRequest)

      This is a variant of listBranches(software.amazon.awssdk.services.codecommit.model.ListBranchesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListBranchesPublisher publisher = client.listBranchesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListBranchesPublisher publisher = client.listBranchesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListBranchesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListBranchesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of null won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listBranches(software.amazon.awssdk.services.codecommit.model.ListBranchesRequest) operation.


      This is a convenience which creates an instance of the ListBranchesRequest.Builder avoiding the need to create one manually via ListBranchesRequest.builder()

      Parameters:
      listBranchesRequest - A Consumer that will call methods on ListBranchesRequest.Builder to create a request. Represents the input of a list branches operation.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listFileCommitHistory

      default CompletableFuture<ListFileCommitHistoryResponse> listFileCommitHistory(ListFileCommitHistoryRequest listFileCommitHistoryRequest)

      Retrieves a list of commits and changes to a specified file.

      Parameters:
      listFileCommitHistoryRequest -
      Returns:
      A Java Future containing the result of the ListFileCommitHistory operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listFileCommitHistory

      default CompletableFuture<ListFileCommitHistoryResponse> listFileCommitHistory(Consumer<ListFileCommitHistoryRequest.Builder> listFileCommitHistoryRequest)

      Retrieves a list of commits and changes to a specified file.


      This is a convenience which creates an instance of the ListFileCommitHistoryRequest.Builder avoiding the need to create one manually via ListFileCommitHistoryRequest.builder()

      Parameters:
      listFileCommitHistoryRequest - A Consumer that will call methods on ListFileCommitHistoryRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListFileCommitHistory operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listFileCommitHistoryPaginator

      default ListFileCommitHistoryPublisher listFileCommitHistoryPaginator(ListFileCommitHistoryRequest listFileCommitHistoryRequest)

      This is a variant of listFileCommitHistory(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListFileCommitHistoryPublisher publisher = client.listFileCommitHistoryPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListFileCommitHistoryPublisher publisher = client.listFileCommitHistoryPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listFileCommitHistory(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryRequest) operation.

      Parameters:
      listFileCommitHistoryRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listFileCommitHistoryPaginator

      default ListFileCommitHistoryPublisher listFileCommitHistoryPaginator(Consumer<ListFileCommitHistoryRequest.Builder> listFileCommitHistoryRequest)

      This is a variant of listFileCommitHistory(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListFileCommitHistoryPublisher publisher = client.listFileCommitHistoryPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListFileCommitHistoryPublisher publisher = client.listFileCommitHistoryPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listFileCommitHistory(software.amazon.awssdk.services.codecommit.model.ListFileCommitHistoryRequest) operation.


      This is a convenience which creates an instance of the ListFileCommitHistoryRequest.Builder avoiding the need to create one manually via ListFileCommitHistoryRequest.builder()

      Parameters:
      listFileCommitHistoryRequest - A Consumer that will call methods on ListFileCommitHistoryRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listPullRequests

      default CompletableFuture<ListPullRequestsResponse> listPullRequests(ListPullRequestsRequest listPullRequestsRequest)

      Returns a list of pull requests for a specified repository. The return list can be refined by pull request status or pull request author ARN.

      Parameters:
      listPullRequestsRequest -
      Returns:
      A Java Future containing the result of the ListPullRequests operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • InvalidAuthorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the author of the pull request, and then try again.
      • AuthorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listPullRequests

      default CompletableFuture<ListPullRequestsResponse> listPullRequests(Consumer<ListPullRequestsRequest.Builder> listPullRequestsRequest)

      Returns a list of pull requests for a specified repository. The return list can be refined by pull request status or pull request author ARN.


      This is a convenience which creates an instance of the ListPullRequestsRequest.Builder avoiding the need to create one manually via ListPullRequestsRequest.builder()

      Parameters:
      listPullRequestsRequest - A Consumer that will call methods on ListPullRequestsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListPullRequests operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • InvalidAuthorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the author of the pull request, and then try again.
      • AuthorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listPullRequestsPaginator

      default ListPullRequestsPublisher listPullRequestsPaginator(ListPullRequestsRequest listPullRequestsRequest)

      This is a variant of listPullRequests(software.amazon.awssdk.services.codecommit.model.ListPullRequestsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListPullRequestsPublisher publisher = client.listPullRequestsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListPullRequestsPublisher publisher = client.listPullRequestsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListPullRequestsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListPullRequestsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listPullRequests(software.amazon.awssdk.services.codecommit.model.ListPullRequestsRequest) operation.

      Parameters:
      listPullRequestsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • InvalidAuthorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the author of the pull request, and then try again.
      • AuthorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listPullRequestsPaginator

      default ListPullRequestsPublisher listPullRequestsPaginator(Consumer<ListPullRequestsRequest.Builder> listPullRequestsRequest)

      This is a variant of listPullRequests(software.amazon.awssdk.services.codecommit.model.ListPullRequestsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListPullRequestsPublisher publisher = client.listPullRequestsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListPullRequestsPublisher publisher = client.listPullRequestsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListPullRequestsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListPullRequestsResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listPullRequests(software.amazon.awssdk.services.codecommit.model.ListPullRequestsRequest) operation.


      This is a convenience which creates an instance of the ListPullRequestsRequest.Builder avoiding the need to create one manually via ListPullRequestsRequest.builder()

      Parameters:
      listPullRequestsRequest - A Consumer that will call methods on ListPullRequestsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • InvalidAuthorArnException The Amazon Resource Name (ARN) is not valid. Make sure that you have provided the full ARN for the author of the pull request, and then try again.
      • AuthorDoesNotExistException The specified Amazon Resource Name (ARN) does not exist in the Amazon Web Services account.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositories

      default CompletableFuture<ListRepositoriesResponse> listRepositories(ListRepositoriesRequest listRepositoriesRequest)

      Gets information about one or more repositories.

      Parameters:
      listRepositoriesRequest - Represents the input of a list repositories operation.
      Returns:
      A Java Future containing the result of the ListRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositories

      default CompletableFuture<ListRepositoriesResponse> listRepositories(Consumer<ListRepositoriesRequest.Builder> listRepositoriesRequest)

      Gets information about one or more repositories.


      This is a convenience which creates an instance of the ListRepositoriesRequest.Builder avoiding the need to create one manually via ListRepositoriesRequest.builder()

      Parameters:
      listRepositoriesRequest - A Consumer that will call methods on ListRepositoriesRequest.Builder to create a request. Represents the input of a list repositories operation.
      Returns:
      A Java Future containing the result of the ListRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositories

      default CompletableFuture<ListRepositoriesResponse> listRepositories()

      Gets information about one or more repositories.

      Returns:
      A Java Future containing the result of the ListRepositories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesForApprovalRuleTemplate

      default CompletableFuture<ListRepositoriesForApprovalRuleTemplateResponse> listRepositoriesForApprovalRuleTemplate(ListRepositoriesForApprovalRuleTemplateRequest listRepositoriesForApprovalRuleTemplateRequest)

      Lists all repositories associated with the specified approval rule template.

      Parameters:
      listRepositoriesForApprovalRuleTemplateRequest -
      Returns:
      A Java Future containing the result of the ListRepositoriesForApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesForApprovalRuleTemplate

      default CompletableFuture<ListRepositoriesForApprovalRuleTemplateResponse> listRepositoriesForApprovalRuleTemplate(Consumer<ListRepositoriesForApprovalRuleTemplateRequest.Builder> listRepositoriesForApprovalRuleTemplateRequest)

      Lists all repositories associated with the specified approval rule template.


      This is a convenience which creates an instance of the ListRepositoriesForApprovalRuleTemplateRequest.Builder avoiding the need to create one manually via ListRepositoriesForApprovalRuleTemplateRequest.builder()

      Parameters:
      listRepositoriesForApprovalRuleTemplateRequest - A Consumer that will call methods on ListRepositoriesForApprovalRuleTemplateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListRepositoriesForApprovalRuleTemplate operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesForApprovalRuleTemplatePaginator

      default ListRepositoriesForApprovalRuleTemplatePublisher listRepositoriesForApprovalRuleTemplatePaginator(ListRepositoriesForApprovalRuleTemplateRequest listRepositoriesForApprovalRuleTemplateRequest)

      This is a variant of listRepositoriesForApprovalRuleTemplate(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesForApprovalRuleTemplatePublisher publisher = client.listRepositoriesForApprovalRuleTemplatePaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesForApprovalRuleTemplatePublisher publisher = client.listRepositoriesForApprovalRuleTemplatePaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listRepositoriesForApprovalRuleTemplate(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateRequest) operation.

      Parameters:
      listRepositoriesForApprovalRuleTemplateRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesForApprovalRuleTemplatePaginator

      default ListRepositoriesForApprovalRuleTemplatePublisher listRepositoriesForApprovalRuleTemplatePaginator(Consumer<ListRepositoriesForApprovalRuleTemplateRequest.Builder> listRepositoriesForApprovalRuleTemplateRequest)

      This is a variant of listRepositoriesForApprovalRuleTemplate(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesForApprovalRuleTemplatePublisher publisher = client.listRepositoriesForApprovalRuleTemplatePaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesForApprovalRuleTemplatePublisher publisher = client.listRepositoriesForApprovalRuleTemplatePaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listRepositoriesForApprovalRuleTemplate(software.amazon.awssdk.services.codecommit.model.ListRepositoriesForApprovalRuleTemplateRequest) operation.


      This is a convenience which creates an instance of the ListRepositoriesForApprovalRuleTemplateRequest.Builder avoiding the need to create one manually via ListRepositoriesForApprovalRuleTemplateRequest.builder()

      Parameters:
      listRepositoriesForApprovalRuleTemplateRequest - A Consumer that will call methods on ListRepositoriesForApprovalRuleTemplateRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidMaxResultsException The specified number of maximum results is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesPaginator

      default ListRepositoriesPublisher listRepositoriesPaginator()

      This is a variant of listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of null won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesPaginator

      default ListRepositoriesPublisher listRepositoriesPaginator(ListRepositoriesRequest listRepositoriesRequest)

      This is a variant of listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of null won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation.

      Parameters:
      listRepositoriesRequest - Represents the input of a list repositories operation.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listRepositoriesPaginator

      default ListRepositoriesPublisher listRepositoriesPaginator(Consumer<ListRepositoriesRequest.Builder> listRepositoriesRequest)

      This is a variant of listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

      The following are few ways to use the response class:

      1) Using the subscribe helper method 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.codecommit.paginators.ListRepositoriesPublisher publisher = client.listRepositoriesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.ListRepositoriesResponse response) { //... };
 });
      As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

      Please notice that the configuration of null won't limit the number of results you get with the paginator. It only limits the number of results in each page.

      Note: If you prefer to have control on service calls, use the listRepositories(software.amazon.awssdk.services.codecommit.model.ListRepositoriesRequest) operation.


      This is a convenience which creates an instance of the ListRepositoriesRequest.Builder avoiding the need to create one manually via ListRepositoriesRequest.builder()

      Parameters:
      listRepositoriesRequest - A Consumer that will call methods on ListRepositoriesRequest.Builder to create a request. Represents the input of a list repositories operation.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidSortByException The specified sort by value is not valid.
      • InvalidOrderException The specified sort order is not valid.
      • InvalidContinuationTokenException The specified continuation token is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)

      Gets information about Amazon Web Servicestags for a specified Amazon Resource Name (ARN) in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.

      Parameters:
      listTagsForResourceRequest -
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)

      Gets information about Amazon Web Servicestags for a specified Amazon Resource Name (ARN) in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.


      This is a convenience which creates an instance of the ListTagsForResourceRequest.Builder avoiding the need to create one manually via ListTagsForResourceRequest.builder()

      Parameters:
      listTagsForResourceRequest - A Consumer that will call methods on ListTagsForResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesByFastForward

      default CompletableFuture<MergeBranchesByFastForwardResponse> mergeBranchesByFastForward(MergeBranchesByFastForwardRequest mergeBranchesByFastForwardRequest)

      Merges two branches using the fast-forward merge strategy.

      Parameters:
      mergeBranchesByFastForwardRequest -
      Returns:
      A Java Future containing the result of the MergeBranchesByFastForward operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesByFastForward

      default CompletableFuture<MergeBranchesByFastForwardResponse> mergeBranchesByFastForward(Consumer<MergeBranchesByFastForwardRequest.Builder> mergeBranchesByFastForwardRequest)

      Merges two branches using the fast-forward merge strategy.


      This is a convenience which creates an instance of the MergeBranchesByFastForwardRequest.Builder avoiding the need to create one manually via MergeBranchesByFastForwardRequest.builder()

      Parameters:
      mergeBranchesByFastForwardRequest - A Consumer that will call methods on MergeBranchesByFastForwardRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergeBranchesByFastForward operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesBySquash

      default CompletableFuture<MergeBranchesBySquashResponse> mergeBranchesBySquash(MergeBranchesBySquashRequest mergeBranchesBySquashRequest)

      Merges two branches using the squash merge strategy.

      Parameters:
      mergeBranchesBySquashRequest -
      Returns:
      A Java Future containing the result of the MergeBranchesBySquash operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesBySquash

      default CompletableFuture<MergeBranchesBySquashResponse> mergeBranchesBySquash(Consumer<MergeBranchesBySquashRequest.Builder> mergeBranchesBySquashRequest)

      Merges two branches using the squash merge strategy.


      This is a convenience which creates an instance of the MergeBranchesBySquashRequest.Builder avoiding the need to create one manually via MergeBranchesBySquashRequest.builder()

      Parameters:
      mergeBranchesBySquashRequest - A Consumer that will call methods on MergeBranchesBySquashRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergeBranchesBySquash operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesByThreeWay

      default CompletableFuture<MergeBranchesByThreeWayResponse> mergeBranchesByThreeWay(MergeBranchesByThreeWayRequest mergeBranchesByThreeWayRequest)

      Merges two specified branches using the three-way merge strategy.

      Parameters:
      mergeBranchesByThreeWayRequest -
      Returns:
      A Java Future containing the result of the MergeBranchesByThreeWay operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergeBranchesByThreeWay

      default CompletableFuture<MergeBranchesByThreeWayResponse> mergeBranchesByThreeWay(Consumer<MergeBranchesByThreeWayRequest.Builder> mergeBranchesByThreeWayRequest)

      Merges two specified branches using the three-way merge strategy.


      This is a convenience which creates an instance of the MergeBranchesByThreeWayRequest.Builder avoiding the need to create one manually via MergeBranchesByThreeWayRequest.builder()

      Parameters:
      mergeBranchesByThreeWayRequest - A Consumer that will call methods on MergeBranchesByThreeWayRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergeBranchesByThreeWay operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • CommitRequiredException A commit was not specified.
      • InvalidCommitException The specified commit is not valid.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidTargetBranchException The specified target branch is not valid.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • BranchDoesNotExistException The specified branch does not exist.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • FileModeRequiredException The commit cannot be created because no file mode has been specified. A file mode is required to update mode permissions for a file.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestByFastForward

      default CompletableFuture<MergePullRequestByFastForwardResponse> mergePullRequestByFastForward(MergePullRequestByFastForwardRequest mergePullRequestByFastForwardRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the fast-forward merge strategy. If the merge is successful, it closes the pull request.

      Parameters:
      mergePullRequestByFastForwardRequest -
      Returns:
      A Java Future containing the result of the MergePullRequestByFastForward operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • ReferenceDoesNotExistException The specified reference does not exist. You must provide a full commit ID.
      • InvalidCommitIdException The specified commit ID is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestByFastForward

      default CompletableFuture<MergePullRequestByFastForwardResponse> mergePullRequestByFastForward(Consumer<MergePullRequestByFastForwardRequest.Builder> mergePullRequestByFastForwardRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the fast-forward merge strategy. If the merge is successful, it closes the pull request.


      This is a convenience which creates an instance of the MergePullRequestByFastForwardRequest.Builder avoiding the need to create one manually via MergePullRequestByFastForwardRequest.builder()

      Parameters:
      mergePullRequestByFastForwardRequest - A Consumer that will call methods on MergePullRequestByFastForwardRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergePullRequestByFastForward operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • ReferenceDoesNotExistException The specified reference does not exist. You must provide a full commit ID.
      • InvalidCommitIdException The specified commit ID is not valid.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestBySquash

      default CompletableFuture<MergePullRequestBySquashResponse> mergePullRequestBySquash(MergePullRequestBySquashRequest mergePullRequestBySquashRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the squash merge strategy. If the merge is successful, it closes the pull request.

      Parameters:
      mergePullRequestBySquashRequest -
      Returns:
      A Java Future containing the result of the MergePullRequestBySquash operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • InvalidCommitIdException The specified commit ID is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestBySquash

      default CompletableFuture<MergePullRequestBySquashResponse> mergePullRequestBySquash(Consumer<MergePullRequestBySquashRequest.Builder> mergePullRequestBySquashRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the squash merge strategy. If the merge is successful, it closes the pull request.


      This is a convenience which creates an instance of the MergePullRequestBySquashRequest.Builder avoiding the need to create one manually via MergePullRequestBySquashRequest.builder()

      Parameters:
      mergePullRequestBySquashRequest - A Consumer that will call methods on MergePullRequestBySquashRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergePullRequestBySquash operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • InvalidCommitIdException The specified commit ID is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestByThreeWay

      default CompletableFuture<MergePullRequestByThreeWayResponse> mergePullRequestByThreeWay(MergePullRequestByThreeWayRequest mergePullRequestByThreeWayRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the three-way merge strategy. If the merge is successful, it closes the pull request.

      Parameters:
      mergePullRequestByThreeWayRequest -
      Returns:
      A Java Future containing the result of the MergePullRequestByThreeWay operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • InvalidCommitIdException The specified commit ID is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • mergePullRequestByThreeWay

      default CompletableFuture<MergePullRequestByThreeWayResponse> mergePullRequestByThreeWay(Consumer<MergePullRequestByThreeWayRequest.Builder> mergePullRequestByThreeWayRequest)

      Attempts to merge the source commit of a pull request into the specified destination branch for that pull request at the specified commit using the three-way merge strategy. If the merge is successful, it closes the pull request.


      This is a convenience which creates an instance of the MergePullRequestByThreeWayRequest.Builder avoiding the need to create one manually via MergePullRequestByThreeWayRequest.builder()

      Parameters:
      mergePullRequestByThreeWayRequest - A Consumer that will call methods on MergePullRequestByThreeWayRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the MergePullRequestByThreeWay operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • InvalidCommitIdException The specified commit ID is not valid.
      • ManualMergeRequiredException The pull request cannot be merged automatically into the destination branch. You must manually merge the branches and resolve any conflicts.
      • TipOfSourceReferenceIsDifferentException The tip of the source branch in the destination repository does not match the tip of the source branch specified in your request. The pull request might have been updated. Make sure that you have the latest changes.
      • TipsDivergenceExceededException The divergence between the tips of the provided commit specifiers is too great to determine whether there might be any merge conflicts. Locally compare the specifiers using git diff or a diff tool.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidConflictDetailLevelException The specified conflict detail level is not valid.
      • InvalidConflictResolutionStrategyException The specified conflict resolution strategy is not valid.
      • InvalidConflictResolutionException The specified conflict resolution list is not valid.
      • ReplacementTypeRequiredException A replacement type is required.
      • InvalidReplacementTypeException Automerge was specified for resolving the conflict, but the specified replacement type is not valid.
      • MultipleConflictResolutionEntriesException More than one conflict resolution entries exists for the conflict. A conflict can have only one conflict resolution entry.
      • ReplacementContentRequiredException USE_NEW_CONTENT was specified, but no replacement content has been provided.
      • MaximumConflictResolutionEntriesExceededException The number of allowed conflict resolution entries was exceeded.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • InvalidReplacementContentException Automerge was specified for resolving the conflict, but the replacement type is not valid or content is missing.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • MaximumFileContentToLoadExceededException The number of files to load exceeds the allowed limit.
      • MaximumItemsToCompareExceededException The number of items to compare between the source or destination branches and the merge base has exceeded the maximum allowed.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • ConcurrentReferenceUpdateException The merge cannot be completed because the target branch has been modified. Another user might have modified the target branch while the merge was in progress. Wait a few minutes, and then try again.
      • PullRequestApprovalRulesNotSatisfiedException The pull request cannot be merged because one or more approval rules applied to the pull request have conditions that have not been met.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • overridePullRequestApprovalRules

      default CompletableFuture<OverridePullRequestApprovalRulesResponse> overridePullRequestApprovalRules(OverridePullRequestApprovalRulesRequest overridePullRequestApprovalRulesRequest)

      Sets aside (overrides) all approval rule requirements for a specified pull request.

      Parameters:
      overridePullRequestApprovalRulesRequest -
      Returns:
      A Java Future containing the result of the OverridePullRequestApprovalRules operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • InvalidOverrideStatusException The override status is not valid. Valid statuses are OVERRIDE and REVOKE.
      • OverrideStatusRequiredException An override status is required, but no value was provided. Valid values include OVERRIDE and REVOKE.
      • OverrideAlreadySetException The pull request has already had its approval rules set to override.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • overridePullRequestApprovalRules

      default CompletableFuture<OverridePullRequestApprovalRulesResponse> overridePullRequestApprovalRules(Consumer<OverridePullRequestApprovalRulesRequest.Builder> overridePullRequestApprovalRulesRequest)

      Sets aside (overrides) all approval rule requirements for a specified pull request.


      This is a convenience which creates an instance of the OverridePullRequestApprovalRulesRequest.Builder avoiding the need to create one manually via OverridePullRequestApprovalRulesRequest.builder()

      Parameters:
      overridePullRequestApprovalRulesRequest - A Consumer that will call methods on OverridePullRequestApprovalRulesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the OverridePullRequestApprovalRules operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • InvalidOverrideStatusException The override status is not valid. Valid statuses are OVERRIDE and REVOKE.
      • OverrideStatusRequiredException An override status is required, but no value was provided. Valid values include OVERRIDE and REVOKE.
      • OverrideAlreadySetException The pull request has already had its approval rules set to override.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentForComparedCommit

      default CompletableFuture<PostCommentForComparedCommitResponse> postCommentForComparedCommit(PostCommentForComparedCommitRequest postCommentForComparedCommitRequest)

      Posts a comment on the comparison between two commits.

      Parameters:
      postCommentForComparedCommitRequest -
      Returns:
      A Java Future containing the result of the PostCommentForComparedCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • InvalidFileLocationException The location of the file is not valid. Make sure that you include the file name and extension.
      • InvalidRelativeFileVersionEnumException Either the enum is not in a valid format, or the specified file version enum is not valid in respect to the current file version.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidFilePositionException The position is not valid. Make sure that the line number exists in the version of the file you want to comment on.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • BeforeCommitIdAndAfterCommitIdAreSameException The before commit ID and the after commit ID are the same, which is not valid. The before commit ID and the after commit ID must be different commit IDs.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • PathRequiredException The folderPath for a location cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentForComparedCommit

      default CompletableFuture<PostCommentForComparedCommitResponse> postCommentForComparedCommit(Consumer<PostCommentForComparedCommitRequest.Builder> postCommentForComparedCommitRequest)

      Posts a comment on the comparison between two commits.


      This is a convenience which creates an instance of the PostCommentForComparedCommitRequest.Builder avoiding the need to create one manually via PostCommentForComparedCommitRequest.builder()

      Parameters:
      postCommentForComparedCommitRequest - A Consumer that will call methods on PostCommentForComparedCommitRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PostCommentForComparedCommit operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • InvalidFileLocationException The location of the file is not valid. Make sure that you include the file name and extension.
      • InvalidRelativeFileVersionEnumException Either the enum is not in a valid format, or the specified file version enum is not valid in respect to the current file version.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidFilePositionException The position is not valid. Make sure that the line number exists in the version of the file you want to comment on.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • BeforeCommitIdAndAfterCommitIdAreSameException The before commit ID and the after commit ID are the same, which is not valid. The before commit ID and the after commit ID must be different commit IDs.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • PathRequiredException The folderPath for a location cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentForPullRequest

      default CompletableFuture<PostCommentForPullRequestResponse> postCommentForPullRequest(PostCommentForPullRequestRequest postCommentForPullRequestRequest)

      Posts a comment on a pull request.

      Parameters:
      postCommentForPullRequestRequest -
      Returns:
      A Java Future containing the result of the PostCommentForPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • InvalidFileLocationException The location of the file is not valid. Make sure that you include the file name and extension.
      • InvalidRelativeFileVersionEnumException Either the enum is not in a valid format, or the specified file version enum is not valid in respect to the current file version.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidFilePositionException The position is not valid. Make sure that the line number exists in the version of the file you want to comment on.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • BeforeCommitIdAndAfterCommitIdAreSameException The before commit ID and the after commit ID are the same, which is not valid. The before commit ID and the after commit ID must be different commit IDs.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • PathRequiredException The folderPath for a location cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentForPullRequest

      default CompletableFuture<PostCommentForPullRequestResponse> postCommentForPullRequest(Consumer<PostCommentForPullRequestRequest.Builder> postCommentForPullRequestRequest)

      Posts a comment on a pull request.


      This is a convenience which creates an instance of the PostCommentForPullRequestRequest.Builder avoiding the need to create one manually via PostCommentForPullRequestRequest.builder()

      Parameters:
      postCommentForPullRequestRequest - A Consumer that will call methods on PostCommentForPullRequestRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PostCommentForPullRequest operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • RepositoryNotAssociatedWithPullRequestException The repository does not contain any pull requests with that pull request ID. Use GetPullRequest to verify the correct repository name for the pull request ID.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • InvalidFileLocationException The location of the file is not valid. Make sure that you include the file name and extension.
      • InvalidRelativeFileVersionEnumException Either the enum is not in a valid format, or the specified file version enum is not valid in respect to the current file version.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidFilePositionException The position is not valid. Make sure that the line number exists in the version of the file you want to comment on.
      • CommitIdRequiredException A commit ID was not specified.
      • InvalidCommitIdException The specified commit ID is not valid.
      • BeforeCommitIdAndAfterCommitIdAreSameException The before commit ID and the after commit ID are the same, which is not valid. The before commit ID and the after commit ID must be different commit IDs.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • CommitDoesNotExistException The specified commit does not exist or no commit was specified, and the specified repository has no default branch.
      • InvalidPathException The specified path is not valid.
      • PathDoesNotExistException The specified path does not exist.
      • PathRequiredException The folderPath for a location cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentReply

      default CompletableFuture<PostCommentReplyResponse> postCommentReply(PostCommentReplyRequest postCommentReplyRequest)

      Posts a comment in reply to an existing comment on a comparison between commits or a pull request.

      Parameters:
      postCommentReplyRequest -
      Returns:
      A Java Future containing the result of the PostCommentReply operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • postCommentReply

      default CompletableFuture<PostCommentReplyResponse> postCommentReply(Consumer<PostCommentReplyRequest.Builder> postCommentReplyRequest)

      Posts a comment in reply to an existing comment on a comparison between commits or a pull request.


      This is a convenience which creates an instance of the PostCommentReplyRequest.Builder avoiding the need to create one manually via PostCommentReplyRequest.builder()

      Parameters:
      postCommentReplyRequest - A Consumer that will call methods on PostCommentReplyRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PostCommentReply operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ClientRequestTokenRequiredException A client request token is required. A client request token is an unique, client-generated idempotency token that, when provided in a request, ensures the request cannot be repeated with a changed parameter. If a request is received with the same parameters and a token is included, the request returns information about the initial request that used that token.
      • InvalidClientRequestTokenException The client request token is not valid.
      • IdempotencyParameterMismatchException The client request token is not valid. Either the token is not in a valid format, or the token has been used in a previous request and cannot be reused.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putCommentReaction

      default CompletableFuture<PutCommentReactionResponse> putCommentReaction(PutCommentReactionRequest putCommentReactionRequest)

      Adds or updates a reaction to a specified comment for the user whose identity is used to make the request. You can only add or update a reaction for yourself. You cannot add, modify, or delete a reaction for another user.

      Parameters:
      putCommentReactionRequest -
      Returns:
      A Java Future containing the result of the PutCommentReaction operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionValueException The value of the reaction is not valid. For more information, see the CodeCommit User Guide.
      • ReactionValueRequiredException A reaction value is required.
      • ReactionLimitExceededException The number of reactions has been exceeded. Reactions are limited to one reaction per user for each individual comment ID.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putCommentReaction

      default CompletableFuture<PutCommentReactionResponse> putCommentReaction(Consumer<PutCommentReactionRequest.Builder> putCommentReactionRequest)

      Adds or updates a reaction to a specified comment for the user whose identity is used to make the request. You can only add or update a reaction for yourself. You cannot add, modify, or delete a reaction for another user.


      This is a convenience which creates an instance of the PutCommentReactionRequest.Builder avoiding the need to create one manually via PutCommentReactionRequest.builder()

      Parameters:
      putCommentReactionRequest - A Consumer that will call methods on PutCommentReactionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PutCommentReaction operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • InvalidReactionValueException The value of the reaction is not valid. For more information, see the CodeCommit User Guide.
      • ReactionValueRequiredException A reaction value is required.
      • ReactionLimitExceededException The number of reactions has been exceeded. Reactions are limited to one reaction per user for each individual comment ID.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putFile

      default CompletableFuture<PutFileResponse> putFile(PutFileRequest putFileRequest)

      Adds or updates a file in a branch in an CodeCommit repository, and generates a commit for the addition in the specified branch.

      Parameters:
      putFileRequest -
      Returns:
      A Java Future containing the result of the PutFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • FileContentRequiredException The file cannot be added because it is empty. Empty files cannot be added to the repository with this API.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidDeletionParameterException The specified deletion parameter is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SameFileContentException The file was not added or updated because the content of the file is exactly the same as the content of that file in the repository and branch that you specified.
      • FileNameConflictsWithDirectoryNameException A file cannot be added to the repository because the specified file name has the same name as a directory in this repository. Either provide another name for the file, or add the file in a directory that does not match the file name.
      • DirectoryNameConflictsWithFileNameException A file cannot be added to the repository because the specified path name has the same name as a file that already exists in this repository. Either provide a different name for the file, or specify a different path for the file.
      • FilePathConflictsWithSubmodulePathException The commit cannot be created because a specified file path points to a submodule. Verify that the destination files have valid file paths that do not point to a submodule.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putFile

      default CompletableFuture<PutFileResponse> putFile(Consumer<PutFileRequest.Builder> putFileRequest)

      Adds or updates a file in a branch in an CodeCommit repository, and generates a commit for the addition in the specified branch.


      This is a convenience which creates an instance of the PutFileRequest.Builder avoiding the need to create one manually via PutFileRequest.builder()

      Parameters:
      putFileRequest - A Consumer that will call methods on PutFileRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PutFile operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryDoesNotExistException The specified repository does not exist.
      • ParentCommitIdRequiredException A parent commit ID is required. To view the full commit ID of a branch in a repository, use GetBranch or a Git command (for example, git pull or git log).
      • InvalidParentCommitIdException The parent commit ID is not valid. The commit ID cannot be empty, and must match the head commit ID for the branch of the repository where you want to add or update a file.
      • ParentCommitDoesNotExistException The parent commit ID is not valid because it does not exist. The specified parent commit ID does not exist in the specified branch of the repository.
      • ParentCommitIdOutdatedException The file could not be added because the provided parent commit ID is not the current tip of the specified branch. To view the full commit ID of the current head of the branch, use GetBranch.
      • FileContentRequiredException The file cannot be added because it is empty. Empty files cannot be added to the repository with this API.
      • FileContentSizeLimitExceededException The file cannot be added because it is too large. The maximum file size is 6 MB, and the combined file content change size is 7 MB. Consider making these changes using a Git client.
      • FolderContentSizeLimitExceededException The commit cannot be created because at least one of the overall changes in the commit results in a folder whose contents exceed the limit of 6 MB. Either reduce the number and size of your changes, or split the changes across multiple folders.
      • PathRequiredException The folderPath for a location cannot be null.
      • InvalidPathException The specified path is not valid.
      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • BranchNameIsTagNameException The specified branch name is not valid because it is a tag name. Enter the name of a branch in the repository. For a list of valid branch names, use ListBranches.
      • InvalidFileModeException The specified file mode permission is not valid. For a list of valid file mode permissions, see PutFile.
      • NameLengthExceededException The user name is not valid because it has exceeded the character limit for author names.
      • InvalidEmailException The specified email address either contains one or more characters that are not allowed, or it exceeds the maximum number of characters allowed for an email address.
      • CommitMessageLengthExceededException The commit message is too long. Provide a shorter string.
      • InvalidDeletionParameterException The specified deletion parameter is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SameFileContentException The file was not added or updated because the content of the file is exactly the same as the content of that file in the repository and branch that you specified.
      • FileNameConflictsWithDirectoryNameException A file cannot be added to the repository because the specified file name has the same name as a directory in this repository. Either provide another name for the file, or add the file in a directory that does not match the file name.
      • DirectoryNameConflictsWithFileNameException A file cannot be added to the repository because the specified path name has the same name as a file that already exists in this repository. Either provide a different name for the file, or specify a different path for the file.
      • FilePathConflictsWithSubmodulePathException The commit cannot be created because a specified file path points to a submodule. Verify that the destination files have valid file paths that do not point to a submodule.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putRepositoryTriggers

      default CompletableFuture<PutRepositoryTriggersResponse> putRepositoryTriggers(PutRepositoryTriggersRequest putRepositoryTriggersRequest)

      Replaces all triggers for a repository. Used to create or delete triggers.

      Parameters:
      putRepositoryTriggersRequest - Represents the input of a put repository triggers operation.
      Returns:
      A Java Future containing the result of the PutRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryTriggersListRequiredException The list of triggers for the repository is required, but was not specified.
      • MaximumRepositoryTriggersExceededException The number of triggers allowed for the repository was exceeded.
      • InvalidRepositoryTriggerNameException The name of the trigger is not valid.
      • InvalidRepositoryTriggerDestinationArnException The Amazon Resource Name (ARN) for the trigger is not valid for the specified destination. The most common reason for this error is that the ARN does not meet the requirements for the service type.
      • InvalidRepositoryTriggerRegionException The Amazon Web Services Region for the trigger target does not match the Amazon Web Services Region for the repository. Triggers must be created in the same Amazon Web Services Region as the target for the trigger.
      • InvalidRepositoryTriggerCustomDataException The custom data provided for the trigger is not valid.
      • MaximumBranchesExceededException The number of branches for the trigger was exceeded.
      • InvalidRepositoryTriggerBranchNameException One or more branch names specified for the trigger is not valid.
      • InvalidRepositoryTriggerEventsException One or more events specified for the trigger is not valid. Check to make sure that all events specified match the requirements for allowed events.
      • RepositoryTriggerNameRequiredException A name for the trigger is required, but was not specified.
      • RepositoryTriggerDestinationArnRequiredException A destination ARN for the target service for the trigger is required, but was not specified.
      • RepositoryTriggerBranchNameListRequiredException At least one branch name is required, but was not specified in the trigger configuration.
      • RepositoryTriggerEventsListRequiredException At least one event for the trigger is required, but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • putRepositoryTriggers

      default CompletableFuture<PutRepositoryTriggersResponse> putRepositoryTriggers(Consumer<PutRepositoryTriggersRequest.Builder> putRepositoryTriggersRequest)

      Replaces all triggers for a repository. Used to create or delete triggers.


      This is a convenience which creates an instance of the PutRepositoryTriggersRequest.Builder avoiding the need to create one manually via PutRepositoryTriggersRequest.builder()

      Parameters:
      putRepositoryTriggersRequest - A Consumer that will call methods on PutRepositoryTriggersRequest.Builder to create a request. Represents the input of a put repository triggers operation.
      Returns:
      A Java Future containing the result of the PutRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryTriggersListRequiredException The list of triggers for the repository is required, but was not specified.
      • MaximumRepositoryTriggersExceededException The number of triggers allowed for the repository was exceeded.
      • InvalidRepositoryTriggerNameException The name of the trigger is not valid.
      • InvalidRepositoryTriggerDestinationArnException The Amazon Resource Name (ARN) for the trigger is not valid for the specified destination. The most common reason for this error is that the ARN does not meet the requirements for the service type.
      • InvalidRepositoryTriggerRegionException The Amazon Web Services Region for the trigger target does not match the Amazon Web Services Region for the repository. Triggers must be created in the same Amazon Web Services Region as the target for the trigger.
      • InvalidRepositoryTriggerCustomDataException The custom data provided for the trigger is not valid.
      • MaximumBranchesExceededException The number of branches for the trigger was exceeded.
      • InvalidRepositoryTriggerBranchNameException One or more branch names specified for the trigger is not valid.
      • InvalidRepositoryTriggerEventsException One or more events specified for the trigger is not valid. Check to make sure that all events specified match the requirements for allowed events.
      • RepositoryTriggerNameRequiredException A name for the trigger is required, but was not specified.
      • RepositoryTriggerDestinationArnRequiredException A destination ARN for the target service for the trigger is required, but was not specified.
      • RepositoryTriggerBranchNameListRequiredException At least one branch name is required, but was not specified in the trigger configuration.
      • RepositoryTriggerEventsListRequiredException At least one event for the trigger is required, but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(TagResourceRequest tagResourceRequest)

      Adds or updates tags for a resource in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.

      Parameters:
      tagResourceRequest -
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • TagsMapRequiredException A map of tags is required.
      • InvalidTagsMapException The map of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • tagResource

      default CompletableFuture<TagResourceResponse> tagResource(Consumer<TagResourceRequest.Builder> tagResourceRequest)

      Adds or updates tags for a resource in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.


      This is a convenience which creates an instance of the TagResourceRequest.Builder avoiding the need to create one manually via TagResourceRequest.builder()

      Parameters:
      tagResourceRequest - A Consumer that will call methods on TagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the TagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • TagsMapRequiredException A map of tags is required.
      • InvalidTagsMapException The map of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • testRepositoryTriggers

      default CompletableFuture<TestRepositoryTriggersResponse> testRepositoryTriggers(TestRepositoryTriggersRequest testRepositoryTriggersRequest)

      Tests the functionality of repository triggers by sending information to the trigger target. If real data is available in the repository, the test sends data from the last commit. If no data is available, sample data is generated.

      Parameters:
      testRepositoryTriggersRequest - Represents the input of a test repository triggers operation.
      Returns:
      A Java Future containing the result of the TestRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryTriggersListRequiredException The list of triggers for the repository is required, but was not specified.
      • MaximumRepositoryTriggersExceededException The number of triggers allowed for the repository was exceeded.
      • InvalidRepositoryTriggerNameException The name of the trigger is not valid.
      • InvalidRepositoryTriggerDestinationArnException The Amazon Resource Name (ARN) for the trigger is not valid for the specified destination. The most common reason for this error is that the ARN does not meet the requirements for the service type.
      • InvalidRepositoryTriggerRegionException The Amazon Web Services Region for the trigger target does not match the Amazon Web Services Region for the repository. Triggers must be created in the same Amazon Web Services Region as the target for the trigger.
      • InvalidRepositoryTriggerCustomDataException The custom data provided for the trigger is not valid.
      • MaximumBranchesExceededException The number of branches for the trigger was exceeded.
      • InvalidRepositoryTriggerBranchNameException One or more branch names specified for the trigger is not valid.
      • InvalidRepositoryTriggerEventsException One or more events specified for the trigger is not valid. Check to make sure that all events specified match the requirements for allowed events.
      • RepositoryTriggerNameRequiredException A name for the trigger is required, but was not specified.
      • RepositoryTriggerDestinationArnRequiredException A destination ARN for the target service for the trigger is required, but was not specified.
      • RepositoryTriggerBranchNameListRequiredException At least one branch name is required, but was not specified in the trigger configuration.
      • RepositoryTriggerEventsListRequiredException At least one event for the trigger is required, but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • testRepositoryTriggers

      default CompletableFuture<TestRepositoryTriggersResponse> testRepositoryTriggers(Consumer<TestRepositoryTriggersRequest.Builder> testRepositoryTriggersRequest)

      Tests the functionality of repository triggers by sending information to the trigger target. If real data is available in the repository, the test sends data from the last commit. If no data is available, sample data is generated.


      This is a convenience which creates an instance of the TestRepositoryTriggersRequest.Builder avoiding the need to create one manually via TestRepositoryTriggersRequest.builder()

      Parameters:
      testRepositoryTriggersRequest - A Consumer that will call methods on TestRepositoryTriggersRequest.Builder to create a request. Represents the input of a test repository triggers operation.
      Returns:
      A Java Future containing the result of the TestRepositoryTriggers operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • RepositoryTriggersListRequiredException The list of triggers for the repository is required, but was not specified.
      • MaximumRepositoryTriggersExceededException The number of triggers allowed for the repository was exceeded.
      • InvalidRepositoryTriggerNameException The name of the trigger is not valid.
      • InvalidRepositoryTriggerDestinationArnException The Amazon Resource Name (ARN) for the trigger is not valid for the specified destination. The most common reason for this error is that the ARN does not meet the requirements for the service type.
      • InvalidRepositoryTriggerRegionException The Amazon Web Services Region for the trigger target does not match the Amazon Web Services Region for the repository. Triggers must be created in the same Amazon Web Services Region as the target for the trigger.
      • InvalidRepositoryTriggerCustomDataException The custom data provided for the trigger is not valid.
      • MaximumBranchesExceededException The number of branches for the trigger was exceeded.
      • InvalidRepositoryTriggerBranchNameException One or more branch names specified for the trigger is not valid.
      • InvalidRepositoryTriggerEventsException One or more events specified for the trigger is not valid. Check to make sure that all events specified match the requirements for allowed events.
      • RepositoryTriggerNameRequiredException A name for the trigger is required, but was not specified.
      • RepositoryTriggerDestinationArnRequiredException A destination ARN for the target service for the trigger is required, but was not specified.
      • RepositoryTriggerBranchNameListRequiredException At least one branch name is required, but was not specified in the trigger configuration.
      • RepositoryTriggerEventsListRequiredException At least one event for the trigger is required, but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(UntagResourceRequest untagResourceRequest)

      Removes tags for a resource in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.

      Parameters:
      untagResourceRequest -
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • TagKeysListRequiredException A list of tag keys is required. The list cannot be empty or null.
      • InvalidTagKeysListException The list of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • untagResource

      default CompletableFuture<UntagResourceResponse> untagResource(Consumer<UntagResourceRequest.Builder> untagResourceRequest)

      Removes tags for a resource in CodeCommit. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.


      This is a convenience which creates an instance of the UntagResourceRequest.Builder avoiding the need to create one manually via UntagResourceRequest.builder()

      Parameters:
      untagResourceRequest - A Consumer that will call methods on UntagResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UntagResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • ResourceArnRequiredException A valid Amazon Resource Name (ARN) for an CodeCommit resource is required. For a list of valid resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • InvalidResourceArnException The value for the resource ARN is not valid. For more information about resources in CodeCommit, see CodeCommit Resources and Operations in the CodeCommit User Guide.
      • TagKeysListRequiredException A list of tag keys is required. The list cannot be empty or null.
      • InvalidTagKeysListException The list of tags is not valid.
      • TooManyTagsException The maximum number of tags for an CodeCommit resource has been exceeded.
      • InvalidSystemTagUsageException The specified tag is not valid. Key names cannot be prefixed with aws:.
      • TagPolicyException The tag policy is not valid.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateContent

      default CompletableFuture<UpdateApprovalRuleTemplateContentResponse> updateApprovalRuleTemplateContent(UpdateApprovalRuleTemplateContentRequest updateApprovalRuleTemplateContentRequest)

      Updates the content of an approval rule template. You can change the number of required approvals, the membership of the approval rule, and whether an approval pool is defined.

      Parameters:
      updateApprovalRuleTemplateContentRequest -
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidApprovalRuleTemplateContentException The content of the approval rule template is not valid.
      • InvalidRuleContentSha256Exception The SHA-256 hash signature for the rule content is not valid.
      • ApprovalRuleTemplateContentRequiredException The content for the approval rule template is empty. You must provide some content for an approval rule template. The content cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateContent

      default CompletableFuture<UpdateApprovalRuleTemplateContentResponse> updateApprovalRuleTemplateContent(Consumer<UpdateApprovalRuleTemplateContentRequest.Builder> updateApprovalRuleTemplateContentRequest)

      Updates the content of an approval rule template. You can change the number of required approvals, the membership of the approval rule, and whether an approval pool is defined.


      This is a convenience which creates an instance of the UpdateApprovalRuleTemplateContentRequest.Builder avoiding the need to create one manually via UpdateApprovalRuleTemplateContentRequest.builder()

      Parameters:
      updateApprovalRuleTemplateContentRequest - A Consumer that will call methods on UpdateApprovalRuleTemplateContentRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidApprovalRuleTemplateContentException The content of the approval rule template is not valid.
      • InvalidRuleContentSha256Exception The SHA-256 hash signature for the rule content is not valid.
      • ApprovalRuleTemplateContentRequiredException The content for the approval rule template is empty. You must provide some content for an approval rule template. The content cannot be null.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateDescription

      default CompletableFuture<UpdateApprovalRuleTemplateDescriptionResponse> updateApprovalRuleTemplateDescription(UpdateApprovalRuleTemplateDescriptionRequest updateApprovalRuleTemplateDescriptionRequest)

      Updates the description for a specified approval rule template.

      Parameters:
      updateApprovalRuleTemplateDescriptionRequest -
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidApprovalRuleTemplateDescriptionException The description for the approval rule template is not valid because it exceeds the maximum characters allowed for a description. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateDescription

      default CompletableFuture<UpdateApprovalRuleTemplateDescriptionResponse> updateApprovalRuleTemplateDescription(Consumer<UpdateApprovalRuleTemplateDescriptionRequest.Builder> updateApprovalRuleTemplateDescriptionRequest)

      Updates the description for a specified approval rule template.


      This is a convenience which creates an instance of the UpdateApprovalRuleTemplateDescriptionRequest.Builder avoiding the need to create one manually via UpdateApprovalRuleTemplateDescriptionRequest.builder()

      Parameters:
      updateApprovalRuleTemplateDescriptionRequest - A Consumer that will call methods on UpdateApprovalRuleTemplateDescriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • InvalidApprovalRuleTemplateDescriptionException The description for the approval rule template is not valid because it exceeds the maximum characters allowed for a description. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateName

      default CompletableFuture<UpdateApprovalRuleTemplateNameResponse> updateApprovalRuleTemplateName(UpdateApprovalRuleTemplateNameRequest updateApprovalRuleTemplateNameRequest)

      Updates the name of a specified approval rule template.

      Parameters:
      updateApprovalRuleTemplateNameRequest -
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateName operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • ApprovalRuleTemplateNameAlreadyExistsException You cannot create an approval rule template with that name because a template with that name already exists in this Amazon Web Services Region for your Amazon Web Services account. Approval rule template names must be unique.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateApprovalRuleTemplateName

      default CompletableFuture<UpdateApprovalRuleTemplateNameResponse> updateApprovalRuleTemplateName(Consumer<UpdateApprovalRuleTemplateNameRequest.Builder> updateApprovalRuleTemplateNameRequest)

      Updates the name of a specified approval rule template.


      This is a convenience which creates an instance of the UpdateApprovalRuleTemplateNameRequest.Builder avoiding the need to create one manually via UpdateApprovalRuleTemplateNameRequest.builder()

      Parameters:
      updateApprovalRuleTemplateNameRequest - A Consumer that will call methods on UpdateApprovalRuleTemplateNameRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateApprovalRuleTemplateName operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidApprovalRuleTemplateNameException The name of the approval rule template is not valid. Template names must be between 1 and 100 valid characters in length. For more information about limits in CodeCommit, see Quotas in the CodeCommit User Guide.
      • ApprovalRuleTemplateNameRequiredException An approval rule template name is required, but was not specified.
      • ApprovalRuleTemplateDoesNotExistException The specified approval rule template does not exist. Verify that the name is correct and that you are signed in to the Amazon Web Services Region where the template was created, and then try again.
      • ApprovalRuleTemplateNameAlreadyExistsException You cannot create an approval rule template with that name because a template with that name already exists in this Amazon Web Services Region for your Amazon Web Services account. Approval rule template names must be unique.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateComment

      default CompletableFuture<UpdateCommentResponse> updateComment(UpdateCommentRequest updateCommentRequest)

      Replaces the contents of a comment.

      Parameters:
      updateCommentRequest -
      Returns:
      A Java Future containing the result of the UpdateComment operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • CommentNotCreatedByCallerException You cannot modify or delete this comment. Only comment authors can modify or delete their comments.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateComment

      default CompletableFuture<UpdateCommentResponse> updateComment(Consumer<UpdateCommentRequest.Builder> updateCommentRequest)

      Replaces the contents of a comment.


      This is a convenience which creates an instance of the UpdateCommentRequest.Builder avoiding the need to create one manually via UpdateCommentRequest.builder()

      Parameters:
      updateCommentRequest - A Consumer that will call methods on UpdateCommentRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateComment operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • CommentContentRequiredException The comment is empty. You must provide some content for a comment. The content cannot be null.
      • CommentContentSizeLimitExceededException The comment is too large. Comments are limited to 10,240 characters.
      • CommentDoesNotExistException No comment exists with the provided ID. Verify that you have used the correct ID, and then try again.
      • CommentIdRequiredException The comment ID is missing or null. A comment ID is required.
      • InvalidCommentIdException The comment ID is not in a valid format. Make sure that you have provided the full comment ID.
      • CommentNotCreatedByCallerException You cannot modify or delete this comment. Only comment authors can modify or delete their comments.
      • CommentDeletedException This comment has already been deleted. You cannot edit or delete a deleted comment.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDefaultBranch

      default CompletableFuture<UpdateDefaultBranchResponse> updateDefaultBranch(UpdateDefaultBranchRequest updateDefaultBranchRequest)

      Sets or changes the default branch name for the specified repository.

      If you use this operation to change the default branch name to the current default branch name, a success message is returned even though the default branch did not change.

      Parameters:
      updateDefaultBranchRequest - Represents the input of an update default branch operation.
      Returns:
      A Java Future containing the result of the UpdateDefaultBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateDefaultBranch

      default CompletableFuture<UpdateDefaultBranchResponse> updateDefaultBranch(Consumer<UpdateDefaultBranchRequest.Builder> updateDefaultBranchRequest)

      Sets or changes the default branch name for the specified repository.

      If you use this operation to change the default branch name to the current default branch name, a success message is returned even though the default branch did not change.


      This is a convenience which creates an instance of the UpdateDefaultBranchRequest.Builder avoiding the need to create one manually via UpdateDefaultBranchRequest.builder()

      Parameters:
      updateDefaultBranchRequest - A Consumer that will call methods on UpdateDefaultBranchRequest.Builder to create a request. Represents the input of an update default branch operation.
      Returns:
      A Java Future containing the result of the UpdateDefaultBranch operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • BranchNameRequiredException A branch name is required, but was not specified.
      • InvalidBranchNameException The specified reference name is not valid.
      • BranchDoesNotExistException The specified branch does not exist.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestApprovalRuleContent

      default CompletableFuture<UpdatePullRequestApprovalRuleContentResponse> updatePullRequestApprovalRuleContent(UpdatePullRequestApprovalRuleContentRequest updatePullRequestApprovalRuleContentRequest)

      Updates the structure of an approval rule created specifically for a pull request. For example, you can change the number of required approvers and the approval pool for approvers.

      Parameters:
      updatePullRequestApprovalRuleContentRequest -
      Returns:
      A Java Future containing the result of the UpdatePullRequestApprovalRuleContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • ApprovalRuleDoesNotExistException The specified approval rule does not exist.
      • InvalidRuleContentSha256Exception The SHA-256 hash signature for the rule content is not valid.
      • ApprovalRuleContentRequiredException The content for the approval rule is empty. You must provide some content for an approval rule. The content cannot be null.
      • InvalidApprovalRuleContentException The content for the approval rule is not valid.
      • CannotModifyApprovalRuleFromTemplateException The approval rule cannot be modified for the pull request because it was created by an approval rule template and applied to the pull request automatically.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestApprovalRuleContent

      default CompletableFuture<UpdatePullRequestApprovalRuleContentResponse> updatePullRequestApprovalRuleContent(Consumer<UpdatePullRequestApprovalRuleContentRequest.Builder> updatePullRequestApprovalRuleContentRequest)

      Updates the structure of an approval rule created specifically for a pull request. For example, you can change the number of required approvers and the approval pool for approvers.


      This is a convenience which creates an instance of the UpdatePullRequestApprovalRuleContentRequest.Builder avoiding the need to create one manually via UpdatePullRequestApprovalRuleContentRequest.builder()

      Parameters:
      updatePullRequestApprovalRuleContentRequest - A Consumer that will call methods on UpdatePullRequestApprovalRuleContentRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdatePullRequestApprovalRuleContent operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • ApprovalRuleNameRequiredException An approval rule name is required, but was not specified.
      • InvalidApprovalRuleNameException The name for the approval rule is not valid.
      • ApprovalRuleDoesNotExistException The specified approval rule does not exist.
      • InvalidRuleContentSha256Exception The SHA-256 hash signature for the rule content is not valid.
      • ApprovalRuleContentRequiredException The content for the approval rule is empty. You must provide some content for an approval rule. The content cannot be null.
      • InvalidApprovalRuleContentException The content for the approval rule is not valid.
      • CannotModifyApprovalRuleFromTemplateException The approval rule cannot be modified for the pull request because it was created by an approval rule template and applied to the pull request automatically.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestApprovalState

      default CompletableFuture<UpdatePullRequestApprovalStateResponse> updatePullRequestApprovalState(UpdatePullRequestApprovalStateRequest updatePullRequestApprovalStateRequest)

      Updates the state of a user's approval on a pull request. The user is derived from the signed-in account when the request is made.

      Parameters:
      updatePullRequestApprovalStateRequest -
      Returns:
      A Java Future containing the result of the UpdatePullRequestApprovalState operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • InvalidApprovalStateException The state for the approval is not valid. Valid values include APPROVE and REVOKE.
      • ApprovalStateRequiredException An approval state is required, but was not specified.
      • PullRequestCannotBeApprovedByAuthorException The approval cannot be applied because the user approving the pull request matches the user who created the pull request. You cannot approve a pull request that you created.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • MaximumNumberOfApprovalsExceededException The number of approvals required for the approval rule exceeds the maximum number allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestApprovalState

      default CompletableFuture<UpdatePullRequestApprovalStateResponse> updatePullRequestApprovalState(Consumer<UpdatePullRequestApprovalStateRequest.Builder> updatePullRequestApprovalStateRequest)

      Updates the state of a user's approval on a pull request. The user is derived from the signed-in account when the request is made.


      This is a convenience which creates an instance of the UpdatePullRequestApprovalStateRequest.Builder avoiding the need to create one manually via UpdatePullRequestApprovalStateRequest.builder()

      Parameters:
      updatePullRequestApprovalStateRequest - A Consumer that will call methods on UpdatePullRequestApprovalStateRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdatePullRequestApprovalState operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidRevisionIdException The revision ID is not valid. Use GetPullRequest to determine the value.
      • RevisionIdRequiredException A revision ID is required, but was not provided.
      • InvalidApprovalStateException The state for the approval is not valid. Valid values include APPROVE and REVOKE.
      • ApprovalStateRequiredException An approval state is required, but was not specified.
      • PullRequestCannotBeApprovedByAuthorException The approval cannot be applied because the user approving the pull request matches the user who created the pull request. You cannot approve a pull request that you created.
      • RevisionNotCurrentException The revision ID provided in the request does not match the current revision ID. Use GetPullRequest to retrieve the current revision ID.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • MaximumNumberOfApprovalsExceededException The number of approvals required for the approval rule exceeds the maximum number allowed.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestDescription

      default CompletableFuture<UpdatePullRequestDescriptionResponse> updatePullRequestDescription(UpdatePullRequestDescriptionRequest updatePullRequestDescriptionRequest)

      Replaces the contents of the description of a pull request.

      Parameters:
      updatePullRequestDescriptionRequest -
      Returns:
      A Java Future containing the result of the UpdatePullRequestDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidDescriptionException The pull request description is not valid. Descriptions cannot be more than 1,000 characters.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestDescription

      default CompletableFuture<UpdatePullRequestDescriptionResponse> updatePullRequestDescription(Consumer<UpdatePullRequestDescriptionRequest.Builder> updatePullRequestDescriptionRequest)

      Replaces the contents of the description of a pull request.


      This is a convenience which creates an instance of the UpdatePullRequestDescriptionRequest.Builder avoiding the need to create one manually via UpdatePullRequestDescriptionRequest.builder()

      Parameters:
      updatePullRequestDescriptionRequest - A Consumer that will call methods on UpdatePullRequestDescriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdatePullRequestDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidDescriptionException The pull request description is not valid. Descriptions cannot be more than 1,000 characters.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestStatus

      default CompletableFuture<UpdatePullRequestStatusResponse> updatePullRequestStatus(UpdatePullRequestStatusRequest updatePullRequestStatusRequest)

      Updates the status of a pull request.

      Parameters:
      updatePullRequestStatusRequest -
      Returns:
      A Java Future containing the result of the UpdatePullRequestStatus operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestStatusUpdateException The pull request status update is not valid. The only valid update is from OPEN to CLOSED.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • PullRequestStatusRequiredException A pull request status is required, but none was provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestStatus

      default CompletableFuture<UpdatePullRequestStatusResponse> updatePullRequestStatus(Consumer<UpdatePullRequestStatusRequest.Builder> updatePullRequestStatusRequest)

      Updates the status of a pull request.


      This is a convenience which creates an instance of the UpdatePullRequestStatusRequest.Builder avoiding the need to create one manually via UpdatePullRequestStatusRequest.builder()

      Parameters:
      updatePullRequestStatusRequest - A Consumer that will call methods on UpdatePullRequestStatusRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdatePullRequestStatus operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • InvalidPullRequestStatusUpdateException The pull request status update is not valid. The only valid update is from OPEN to CLOSED.
      • InvalidPullRequestStatusException The pull request status is not valid. The only valid values are OPEN and CLOSED.
      • PullRequestStatusRequiredException A pull request status is required, but none was provided.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestTitle

      default CompletableFuture<UpdatePullRequestTitleResponse> updatePullRequestTitle(UpdatePullRequestTitleRequest updatePullRequestTitleRequest)

      Replaces the title of a pull request.

      Parameters:
      updatePullRequestTitleRequest -
      Returns:
      A Java Future containing the result of the UpdatePullRequestTitle operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • TitleRequiredException A pull request title is required. It cannot be empty or null.
      • InvalidTitleException The title of the pull request is not valid. Pull request titles cannot exceed 100 characters in length.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updatePullRequestTitle

      default CompletableFuture<UpdatePullRequestTitleResponse> updatePullRequestTitle(Consumer<UpdatePullRequestTitleRequest.Builder> updatePullRequestTitleRequest)

      Replaces the title of a pull request.


      This is a convenience which creates an instance of the UpdatePullRequestTitleRequest.Builder avoiding the need to create one manually via UpdatePullRequestTitleRequest.builder()

      Parameters:
      updatePullRequestTitleRequest - A Consumer that will call methods on UpdatePullRequestTitleRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdatePullRequestTitle operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • PullRequestDoesNotExistException The pull request ID could not be found. Make sure that you have specified the correct repository name and pull request ID, and then try again.
      • InvalidPullRequestIdException The pull request ID is not valid. Make sure that you have provided the full ID and that the pull request is in the specified repository, and then try again.
      • PullRequestIdRequiredException A pull request ID is required, but none was provided.
      • TitleRequiredException A pull request title is required. It cannot be empty or null.
      • InvalidTitleException The title of the pull request is not valid. Pull request titles cannot exceed 100 characters in length.
      • PullRequestAlreadyClosedException The pull request status cannot be updated because it is already closed.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryDescription

      default CompletableFuture<UpdateRepositoryDescriptionResponse> updateRepositoryDescription(UpdateRepositoryDescriptionRequest updateRepositoryDescriptionRequest)

      Sets or changes the comment or description for a repository.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.

      Parameters:
      updateRepositoryDescriptionRequest - Represents the input of an update repository description operation.
      Returns:
      A Java Future containing the result of the UpdateRepositoryDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidRepositoryDescriptionException The specified repository description is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryDescription

      default CompletableFuture<UpdateRepositoryDescriptionResponse> updateRepositoryDescription(Consumer<UpdateRepositoryDescriptionRequest.Builder> updateRepositoryDescriptionRequest)

      Sets or changes the comment or description for a repository.

      The description field for a repository accepts all HTML characters and all valid Unicode characters. Applications that do not HTML-encode the description and display it in a webpage can expose users to potentially malicious code. Make sure that you HTML-encode the description field in any application that uses this API to display the repository description on a webpage.


      This is a convenience which creates an instance of the UpdateRepositoryDescriptionRequest.Builder avoiding the need to create one manually via UpdateRepositoryDescriptionRequest.builder()

      Parameters:
      updateRepositoryDescriptionRequest - A Consumer that will call methods on UpdateRepositoryDescriptionRequest.Builder to create a request. Represents the input of an update repository description operation.
      Returns:
      A Java Future containing the result of the UpdateRepositoryDescription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • InvalidRepositoryDescriptionException The specified repository description is not valid.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryEncryptionKey

      default CompletableFuture<UpdateRepositoryEncryptionKeyResponse> updateRepositoryEncryptionKey(UpdateRepositoryEncryptionKeyRequest updateRepositoryEncryptionKeyRequest)

      Updates the Key Management Service encryption key used to encrypt and decrypt a CodeCommit repository.

      Parameters:
      updateRepositoryEncryptionKeyRequest -
      Returns:
      A Java Future containing the result of the UpdateRepositoryEncryptionKey operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionKeyRequiredException A KMS encryption key ID is required but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyInvalidIdException The Key Management Service encryption key is not valid.
      • EncryptionKeyInvalidUsageException A KMS encryption key was used to try and encrypt or decrypt a repository, but either the repository or the key was not in a valid state to support the operation.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryEncryptionKey

      default CompletableFuture<UpdateRepositoryEncryptionKeyResponse> updateRepositoryEncryptionKey(Consumer<UpdateRepositoryEncryptionKeyRequest.Builder> updateRepositoryEncryptionKeyRequest)

      Updates the Key Management Service encryption key used to encrypt and decrypt a CodeCommit repository.


      This is a convenience which creates an instance of the UpdateRepositoryEncryptionKeyRequest.Builder avoiding the need to create one manually via UpdateRepositoryEncryptionKeyRequest.builder()

      Parameters:
      updateRepositoryEncryptionKeyRequest - A Consumer that will call methods on UpdateRepositoryEncryptionKeyRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the UpdateRepositoryEncryptionKey operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • EncryptionKeyRequiredException A KMS encryption key ID is required but was not specified.
      • EncryptionIntegrityChecksFailedException An encryption integrity check failed.
      • EncryptionKeyAccessDeniedException An encryption key could not be accessed.
      • EncryptionKeyInvalidIdException The Key Management Service encryption key is not valid.
      • EncryptionKeyInvalidUsageException A KMS encryption key was used to try and encrypt or decrypt a repository, but either the repository or the key was not in a valid state to support the operation.
      • EncryptionKeyDisabledException The encryption key is disabled.
      • EncryptionKeyNotFoundException No encryption key was found.
      • EncryptionKeyUnavailableException The encryption key is not available.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryName

      default CompletableFuture<UpdateRepositoryNameResponse> updateRepositoryName(UpdateRepositoryNameRequest updateRepositoryNameRequest)

      Renames a repository. The repository name must be unique across the calling Amazon Web Services account. Repository names are limited to 100 alphanumeric, dash, and underscore characters, and cannot include certain characters. The suffix .git is prohibited. For more information about the limits on repository names, see Quotas in the CodeCommit User Guide.

      Parameters:
      updateRepositoryNameRequest - Represents the input of an update repository description operation.
      Returns:
      A Java Future containing the result of the UpdateRepositoryName operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameExistsException The specified repository name already exists.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • updateRepositoryName

      default CompletableFuture<UpdateRepositoryNameResponse> updateRepositoryName(Consumer<UpdateRepositoryNameRequest.Builder> updateRepositoryNameRequest)

      Renames a repository. The repository name must be unique across the calling Amazon Web Services account. Repository names are limited to 100 alphanumeric, dash, and underscore characters, and cannot include certain characters. The suffix .git is prohibited. For more information about the limits on repository names, see Quotas in the CodeCommit User Guide.


      This is a convenience which creates an instance of the UpdateRepositoryNameRequest.Builder avoiding the need to create one manually via UpdateRepositoryNameRequest.builder()

      Parameters:
      updateRepositoryNameRequest - A Consumer that will call methods on UpdateRepositoryNameRequest.Builder to create a request. Represents the input of an update repository description operation.
      Returns:
      A Java Future containing the result of the UpdateRepositoryName operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • RepositoryDoesNotExistException The specified repository does not exist.
      • RepositoryNameExistsException The specified repository name already exists.
      • RepositoryNameRequiredException A repository name is required, but was not specified.
      • InvalidRepositoryNameException A specified repository name is not valid.

        This exception occurs only when a specified repository name is not valid. Other exceptions occur when a required repository parameter is missing, or when a specified repository does not exist.

      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • CodeCommitException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • serviceClientConfiguration

      default CodeCommitServiceClientConfiguration serviceClientConfiguration()
      Description copied from interface: SdkClient
      The SDK service client configuration exposes client settings to the user, e.g., ClientOverrideConfiguration
      Specified by:
      serviceClientConfiguration in interface AwsClient
      Specified by:
      serviceClientConfiguration in interface SdkClient
      Returns:
      SdkServiceClientConfiguration

    • create

      static CodeCommitAsyncClient create()
      Create a CodeCommitAsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.

    • builder

      static CodeCommitAsyncClientBuilder builder()
      Create a builder that can be used to configure and create a CodeCommitAsyncClient.