-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/gitlab_repository_file: Mitigate parallelism limitation #964
resource/gitlab_repository_file: Mitigate parallelism limitation #964
Conversation
66420da
to
35a966d
Compare
8579b91
to
2ae4582
Compare
2ae4582
to
fa82d67
Compare
e309bf4
to
5ecb57c
Compare
This pull request has merge conflicts. Please rebase your branch onto |
5ecb57c
to
e189068
Compare
Conflicts are resolved. Thank you! 😀 |
This functionality has been released in v3.13.0 of the Terraform GitLab Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue. Thank you! |
This change set implements the following two measures to mitigate / remove the parallelism issues we were having as described in #940:
gitlab_repository_file
resource to make an API call (no matter to which project or file)The first mitigates that resources within an apply / destroy are queued and the second mitigates the case when something else outside of terraform changes the repository state. Both combined are good mitigations for the issue at hand.
The drawback of this change is that it'll slow down certain terraform configurations - necessarily and unnecessarily in cases were a files in different repositories / projects are changed, but still queued. I think that's a limitation I'm willing to take for the benefits it provides.
Closes #940