|
3 | 3 | page_title: "gitlab_repository_file Resource - terraform-provider-gitlab"
|
4 | 4 | subcategory: ""
|
5 | 5 | description: |-
|
6 |
| - This resource allows you to create and manage GitLab repository files. |
7 |
| - Limitations: |
8 |
| - The GitLab Repository Files API https://docs.gitlab.com/ee/api/repository_files.html |
9 |
| - can only create, update or delete a single file at the time. |
10 |
| - The API will also |
11 |
| - fail with a 400 https://docs.gitlab.com/ee/api/repository_files.html#update-existing-file-in-repository |
12 |
| - response status code if the underlying repository is changed while the API tries to make changes. |
13 |
| - Therefore, it's recommended to make sure that you execute it with |
14 |
| - -parallelism=1 https://www.terraform.io/docs/cli/commands/apply.html#parallelism-n |
15 |
| - and that no other entity than the terraform at hand makes changes to the |
16 |
| - underlying repository while it's executing. |
| 6 | + The gitlab_repository_file resource allows to manage the lifecycle of a file within a repository. |
| 7 | + ~> Limitations: The GitLab Repository Files API https://docs.gitlab.com/ee/api/repository_files.html can only create, update or delete a single file at the time. The API will also fail with a 400 https://docs.gitlab.com/ee/api/repository_files.html#update-existing-file-in-repository response status code if the underlying repository is changed while the API tries to make changes. Therefore, it's recommended to make sure that you execute it with -parallelism=1 https://www.terraform.io/docs/cli/commands/apply.html#parallelism-n and that no other entity than the terraform at hand makes changes to the underlying repository while it's executing. |
| 8 | + Upstream API: GitLab REST API docs https://docs.gitlab.com/ee/api/repository_files.html |
17 | 9 | ---
|
18 | 10 |
|
19 | 11 | # gitlab_repository_file (Resource)
|
20 | 12 |
|
21 |
| -This resource allows you to create and manage GitLab repository files. |
| 13 | +The `gitlab_repository_file` resource allows to manage the lifecycle of a file within a repository. |
22 | 14 |
|
23 |
| -**Limitations**: |
| 15 | +~> **Limitations**: The [GitLab Repository Files API](https://docs.gitlab.com/ee/api/repository_files.html) can only create, update or delete a single file at the time. The API will also [fail with a 400](https://docs.gitlab.com/ee/api/repository_files.html#update-existing-file-in-repository) response status code if the underlying repository is changed while the API tries to make changes. Therefore, it's recommended to make sure that you execute it with [-parallelism=1](https://www.terraform.io/docs/cli/commands/apply.html#parallelism-n) and that no other entity than the terraform at hand makes changes to the underlying repository while it's executing. |
24 | 16 |
|
25 |
| -The [GitLab Repository Files API](https://docs.gitlab.com/ee/api/repository_files.html) |
26 |
| -can only create, update or delete a single file at the time. |
27 |
| -The API will also |
28 |
| -[fail with a `400`](https://docs.gitlab.com/ee/api/repository_files.html#update-existing-file-in-repository) |
29 |
| -response status code if the underlying repository is changed while the API tries to make changes. |
30 |
| -Therefore, it's recommended to make sure that you execute it with |
31 |
| -[`-parallelism=1`](https://www.terraform.io/docs/cli/commands/apply.html#parallelism-n) |
32 |
| -and that no other entity than the terraform at hand makes changes to the |
33 |
| -underlying repository while it's executing. |
| 17 | +**Upstream API**: [GitLab REST API docs](https://docs.gitlab.com/ee/api/repository_files.html) |
34 | 18 |
|
35 | 19 | ## Example Usage
|
36 | 20 |
|
|
0 commit comments