Timo Furrer
Timo Furrer
This change will support the two options when removing a user from a group using `gitlab_group_membership`. These are `skip_subresources_on_destroy` and `unassign_issuables_on_destroy`. Both default to `false` and the change is backwards...
Refs: #1132
This change set implements the new `gitlab_application_settings` resource which provides a way to change the GitLab Application Settings using the API at https://docs.gitlab.com/ee/api/settings.html#change-application-settings. Even though I suggest that we can...
This will fix the acceptance testing instance to have a proper external URL configured. With that redirects within GitLab will work (e.g. from the WebIDE back to the repository) and...
Closes: #69 Blocked by: * https://github.com/xanzy/go-gitlab/pull/1407 The PR above highlights the issue why this is blocked: basically go-gitlab doesn't support nullable fields in responses, which would be required for the...
### Feature Description To prevent issues like #1167 it would be awesome to have specific tests to be configured and ran with a non-admin token. I think in general it...
This issue is a follow up from the [2022-06-01 Community Hour](https://docs.google.com/document/d/1-rgmylTUlO2lPRmbmGk0aB-mktg8nYu0NxOkFw9bo_M/edit) where we've discussed options to migrate away from Google Calendar to improve a few current issues (like calendar updates,...
We seem to have an issue in the acceptance tests running on `main` branch: https://github.com/gitlabhq/terraform-provider-gitlab/runs/6124104979?check_suite_focus=true#step:7:217 ``` === RUN TestAccGitlabProject_basic resource_gitlab_project_test.go:123: Step 1/19 error: After applying this test step and performing...
A test just randomly failed for the first time (at least for me ^^): see https://github.com/gitlabhq/terraform-provider-gitlab/runs/6970761305?check_suite_focus=true#step:6:578 ``` === CONT TestAccGitlabProject_basic resource_gitlab_project_test.go:122: Skipping step 6/19 due to SkipFunc resource_gitlab_project_test.go:122: Skipping step...
How do handle cases where GitLab implicitly creates a resource resulting in tf ownership confusion
There has been a discussion in #266 about what to do in the following situation: ```hcl resource "gitlab_group" "group" { } resource "gitlab_group_membership" "membership" { user_id = } ``` ......