[NOTE] How to trigger a specific replication

[moooofly]

by harborctl

• "GET /policies/replication/{id}"
• "POST /replications"

[#1084#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$./harborctl policy replication get -i 1
==> GET https://localhost/api/policies/replication/1
<==
<== Rsp Status: 200 OK
<== Rsp Body: {
  "id": 1,
  "name": "sync-to-somewhere",
  "description": "",
  "filters": null,
  "replicate_deletion": false,
  "trigger": {
    "kind": "Manual",
    "schedule_param": null
  },
  "projects": [
    {
      "project_id": 10,
      "owner_id": 1,
      "name": "temp_9",
      "creation_time": "2018-11-02T06:58:29Z",
      "update_time": "2018-11-02T06:58:29Z",
      "deleted": false,
      "owner_name": "",
      "togglable": false,
      "current_user_role_id": 0,
      "repo_count": 0,
      "metadata": {
        "public": "true"
      }
    }
  ],
  "targets": [
    {
      "id": 1,
      "endpoint": "http://11.11.11.22",
      "name": "fake endpoint",
      "username": "admin",
      "password": "",
      "type": 0,
      "insecure": true,
      "creation_time": "2018-11-07T14:42:31.876842Z",
      "update_time": "2018-11-07T14:42:31.876842Z"
    }
  ],
  "creation_time": "2018-11-07T14:43:11Z",
  "update_time": "2018-11-07T14:43:11Z",
  "replicate_existing_image_now": false,
  "error_job_count": 5
}
[#1085#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$

[#1085#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$./harborctl replication trigger -i 1
==> POST https://localhost/api/replications
<==
<== Rsp Status: 200 OK
<== Rsp Body:
[#1086#root@ubuntu-1604 /go/src/github.com/moooofly/harborctl]$

[moooofly]

UPDATE:

• Based on my test result, this API can work as expect at Harbor v1.5.0-d59c257e.
• One thing should pay attention to is that it triggers replication action at policy level (by policy_id), in another word, all repositories under the projects related to this specific policy ID will be replicated.
• The truth is: usually, I just want to replicate only one repository (or a small mount of repositories) to the remote endpoint for the sake of transferring error happened by chance. If it plays at policy level, a lot of useless works will be done.