github.com/argoproj/argo-cd/v3@v3.2.1/docs/proposals/manifest-hydrator/commit-server/README.md (about)

     1  # Commit Server
     2  
     3  The Argo CD Commit Server provides push access to git repositories for hydrated manifests.
     4  
     5  The server exposes a gRPC service which accepts requests to push hydrated manifests to a git repository. This is the interface:
     6  
     7  ```protobuf
     8  // CommitManifests represents the caller's request for some Kubernetes manifests to be pushed to a git repository.
     9  message CommitManifests {
    10    // repoURL is the URL of the repo we're pushing to. HTTPS or SSH URLs are acceptable.
    11    required string repoURL = 1;
    12    // targetBranch is the name of the branch we're pushing to.
    13    required string targetBranch = 2;
    14    // drySHA is the full SHA256 hash of the "dry commit" from which the manifests were hydrated.
    15    required string drySHA = 3;
    16    // commitAuthor is the name of the author of the dry commit.
    17    required string commitAuthor = 4;
    18    // commitMessage is the short commit message from the dry commit.
    19    required string commitMessage = 5;
    20    // commitTime is the dry commit timestamp.
    21    required string commitTime = 6;
    22    // details holds the information about the actual hydrated manifests.
    23    repeated CommitPathDetails details = 7;
    24  }
    25  
    26  // CommitManifestDetails represents the details about a 
    27  message CommitPathDetails {
    28    // path is the path to the directory to which these manifests should be written.
    29    required string path = 1;
    30    // manifests is a list of JSON documents representing the Kubernetes manifests.
    31    repeated string manifests = 2;
    32    // readme is a string which will be written to a README.md alongside the manifest.yaml. 
    33    required string readme = 3;
    34  }
    35  
    36  message CommitManifestsResponse {
    37  }
    38  ```