Timo Furrer
Timo Furrer
We've had a brief discussion in #1073 about the project structure w.r.t to the file hierarchy / naming and go packages. We kinda agree that with the growing amount of...
We should consider implementing checks to verify if the GitLab instance is correctly spun up. The best place is probably the `healthcheck-and-setup.sh` or `await-healthy.sh` script. _Originally posted by @timofurrer in...
Remove the code here: https://github.com/gitlabhq/terraform-provider-gitlab/blob/b3f88599446367aed2353dac0b4a1bf9e67d4bfe/internal/provider/resource_gitlab_service_slack.go#L257 ... which adds backwards-compatibility for some older provider versions.
Our group-resources should support path group ID and group paths with namespaces as group identifier. We should align the attributes to `group` instead of `group_id`.
Our project-resources should support path project ID and project paths with namespaces as project identifier. We should align the attributes to `project` instead of `project_id`.
Remove code for backward-compatibility: https://github.com/gitlabhq/terraform-provider-gitlab/blob/b3f88599446367aed2353dac0b4a1bf9e67d4bfe/internal/provider/resource_gitlab_repository_file.go#L110
The service endpoint in the GitLab API has been renamed from `service` to `integration`, we should follow that and rename the resources we provide for them, e.g. * `gitlab_service_external_wiki` *...
Remove the code to guarantee backwards-compatibility with some older versions: https://github.com/gitlabhq/terraform-provider-gitlab/blob/b3f88599446367aed2353dac0b4a1bf9e67d4bfe/internal/provider/resource_gitlab_project_variable.go#L76
The `gitlab_project_hook` 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 current implementation of the `gitlab_pipeline_trigger` 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...