Timo Furrer
Timo Furrer
The current implementation of the `gitlab_pipeline_schedule` ID doesn't allow to use the passthrough importer, because it doesn't contain all the information required to read it. The goal is to use...
The current implementation of the `gitlab_pipeline_schedule_variable` ID doesn't allow to use the passthrough importer, because it doesn't contain all the information required to read it. The goal is to use...
see details in: * #869
The `gitlab_group_label` resource currently uses the ID format: ``. This is not enough to use the passthrough importer, because the group is missing. The goal is to: * implement an...
The `gitlab_label` resource should be renamed to `gitlab_project_label` to match our used naming scheme. Additionally it currently uses the ID format: ``. This is not enough to use the passthrough...
The `gitlab_deploy_token` resource currently uses the ID format: . This is not enough to use the passthrough importer, because the project is missing. The goal is to: * implement an...
The `gitlab_deploy_key` resource currently uses the ID format: ``. This is not enough to use the passthrough importer, because the `project` is missing. The goal is to: * implement an...
Let's make sure that we properly configure the certs for the acceptance tests GitLab instance regarding subdomains etc. *** I kinda dislike the naming of the re-used cert files here...
During one of the CE acceptance test runs I've got this failure: https://github.com/gitlabhq/terraform-provider-gitlab/runs/4993701443?check_suite_focus=true#step:6:93 > === RUN TestAccGitlabLabel_basic > resource_gitlab_label_test.go:17: Step 5/5 error: Error running apply: exit status 1 > >...
The current `gitlab_service_slack` resource is missing a few new-ish parameters, like the `deployment_channel` and `deployment_events`. The goal of this issue is to update this resource if all available parameters. Follow...