2020-06-10 11:08:07 -04:00
---
stage: Create
group: Gitaly
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
type: reference
---
2020-07-13 17:09:24 -04:00
# Project repository storage moves API **(CORE ONLY)**
2020-05-15 05:07:59 -04:00
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31285) in GitLab 13.0.
2020-11-01 22:08:43 -05:00
Project repositories including wiki and design repositories can be moved between storages. This can be useful when
2020-08-27 14:10:29 -04:00
[migrating to Gitaly Cluster ](../administration/gitaly/praefect.md#migrate-existing-repositories-to-gitaly-cluster ),
for example.
As project repository storage moves are processed, they transition through different states. Values
of `state` are:
- `initial`
- `scheduled`
- `started`
- `finished`
- `failed`
- `replicated`
2020-10-29 23:08:51 -04:00
- `cleanup failed`
2020-08-27 14:10:29 -04:00
2020-10-27 20:08:34 -04:00
To ensure data integrity, projects are put in a temporary read-only state for the
duration of the move. During this time, users receive a `The repository is temporarily
read-only. Please try again later.` message if they try to push new commits.
2020-08-27 14:10:29 -04:00
This API requires you to [authenticate yourself ](README.md#authentication ) as an administrator.
2020-05-15 05:07:59 -04:00
2020-10-29 02:08:45 -04:00
## Limitations
2020-10-29 14:09:11 -04:00
- The repositories associated with snippets [can't be moved with the API ](https://gitlab.com/groups/gitlab-org/-/epics/3393 ).
- Group-level wikis [can't be moved with the API ](https://gitlab.com/gitlab-org/gitlab/-/issues/219003 ).
2020-10-29 02:08:45 -04:00
2020-05-15 05:07:59 -04:00
## Retrieve all project repository storage moves
2020-05-19 23:08:04 -04:00
```plaintext
2020-05-15 05:07:59 -04:00
GET /project_repository_storage_moves
```
By default, `GET` requests return 20 results at a time because the API results
are [paginated ](README.md#pagination ).
Example request:
```shell
2020-07-13 17:09:24 -04:00
curl --header "PRIVATE-TOKEN: < your_access_token > " "https://gitlab.example.com/api/v4/project_repository_storage_moves"
2020-05-15 05:07:59 -04:00
```
Example response:
```json
[
{
"id": 1,
"created_at": "2020-05-07T04:27:17.234Z",
"state": "scheduled",
"source_storage_name": "default",
"destination_storage_name": "storage2",
"project": {
"id": 1,
"description": null,
"name": "project1",
"name_with_namespace": "John Doe2 / project1",
"path": "project1",
"path_with_namespace": "namespace1/project1",
"created_at": "2020-05-07T04:27:17.016Z"
}
]
```
2020-05-29 17:08:35 -04:00
## Retrieve all repository storage moves for a project
```plaintext
GET /projects/:project_id/repository_storage_moves
```
By default, `GET` requests return 20 results at a time because the API results
are [paginated ](README.md#pagination ).
Parameters:
| Attribute | Type | Required | Description |
| --------- | ---- | -------- | ----------- |
2020-06-15 20:08:33 -04:00
| `project_id` | integer | yes | ID of the project |
2020-05-29 17:08:35 -04:00
Example request:
```shell
2020-07-13 17:09:24 -04:00
curl --header "PRIVATE-TOKEN: < your_access_token > " "https://gitlab.example.com/api/v4/projects/1/repository_storage_moves"
2020-05-29 17:08:35 -04:00
```
Example response:
```json
[
{
"id": 1,
"created_at": "2020-05-07T04:27:17.234Z",
"state": "scheduled",
"source_storage_name": "default",
"destination_storage_name": "storage2",
"project": {
"id": 1,
"description": null,
"name": "project1",
"name_with_namespace": "John Doe2 / project1",
"path": "project1",
"path_with_namespace": "namespace1/project1",
"created_at": "2020-05-07T04:27:17.016Z"
}
]
```
2020-05-15 05:07:59 -04:00
## Get a single project repository storage move
2020-05-19 23:08:04 -04:00
```plaintext
2020-05-29 17:08:35 -04:00
GET /project_repository_storage_moves/:repository_storage_id
2020-05-15 05:07:59 -04:00
```
Parameters:
| Attribute | Type | Required | Description |
| --------- | ---- | -------- | ----------- |
2020-06-15 20:08:33 -04:00
| `repository_storage_id` | integer | yes | ID of the project repository storage move |
2020-05-15 05:07:59 -04:00
Example request:
```shell
2020-07-13 17:09:24 -04:00
curl --header "PRIVATE-TOKEN: < your_access_token > " "https://gitlab.example.com/api/v4/project_repository_storage_moves/1"
2020-05-15 05:07:59 -04:00
```
Example response:
```json
{
"id": 1,
"created_at": "2020-05-07T04:27:17.234Z",
"state": "scheduled",
"source_storage_name": "default",
"destination_storage_name": "storage2",
"project": {
"id": 1,
"description": null,
"name": "project1",
"name_with_namespace": "John Doe2 / project1",
"path": "project1",
"path_with_namespace": "namespace1/project1",
"created_at": "2020-05-07T04:27:17.016Z"
}
```
2020-05-29 17:08:35 -04:00
## Get a single repository storage move for a project
```plaintext
2020-06-15 20:08:33 -04:00
GET /projects/:project_id/repository_storage_moves/:repository_storage_id
2020-05-29 17:08:35 -04:00
```
Parameters:
| Attribute | Type | Required | Description |
| --------- | ---- | -------- | ----------- |
2020-06-15 20:08:33 -04:00
| `project_id` | integer | yes | ID of the project |
| `repository_storage_id` | integer | yes | ID of the project repository storage move |
2020-05-29 17:08:35 -04:00
Example request:
```shell
2020-07-13 17:09:24 -04:00
curl --header "PRIVATE-TOKEN: < your_access_token > " "https://gitlab.example.com/api/v4/projects/1/repository_storage_moves/1"
2020-06-15 20:08:33 -04:00
```
Example response:
```json
{
"id": 1,
"created_at": "2020-05-07T04:27:17.234Z",
"state": "scheduled",
"source_storage_name": "default",
"destination_storage_name": "storage2",
"project": {
"id": 1,
"description": null,
"name": "project1",
"name_with_namespace": "John Doe2 / project1",
"path": "project1",
"path_with_namespace": "namespace1/project1",
"created_at": "2020-05-07T04:27:17.016Z"
}
```
## Schedule a repository storage move for a project
2020-11-01 22:08:43 -05:00
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34119) in GitLab 13.1.
> - [Introduced](https://gitlab.com/gitlab-org/gitaly/-/issues/2618) in GitLab 13.3, original repository is automatically removed after successful move and integrity check.
CAUTION: **Caution:**
Before GitLab 13.3, a repository move worked more like a repository copy as the
original repository was not deleted from the original storage disk location and
had to be manually cleaned up.
2020-06-15 20:08:33 -04:00
```plaintext
POST /projects/:project_id/repository_storage_moves
```
Parameters:
| Attribute | Type | Required | Description |
| --------- | ---- | -------- | ----------- |
| `project_id` | integer | yes | ID of the project |
2020-10-22 17:10:39 -04:00
| `destination_storage_name` | string | no | Name of the destination storage shard. In [GitLab 13.5 and later ](https://gitlab.com/gitlab-org/gitaly/-/issues/3209 ), the storage is selected automatically if not provided |
2020-06-15 20:08:33 -04:00
Example request:
```shell
2020-11-04 22:09:03 -05:00
curl --request POST --header "PRIVATE-TOKEN: < your_access_token > " --header "Content-Type: application/json" \
2020-07-13 17:09:24 -04:00
--data '{"destination_storage_name":"storage2"}' "https://gitlab.example.com/api/v4/projects/1/repository_storage_moves"
2020-05-29 17:08:35 -04:00
```
Example response:
```json
{
"id": 1,
"created_at": "2020-05-07T04:27:17.234Z",
"state": "scheduled",
"source_storage_name": "default",
"destination_storage_name": "storage2",
"project": {
"id": 1,
"description": null,
"name": "project1",
"name_with_namespace": "John Doe2 / project1",
"path": "project1",
"path_with_namespace": "namespace1/project1",
"created_at": "2020-05-07T04:27:17.016Z"
}
```