terraform-provider-gitlab
terraform-provider-gitlab copied to clipboard
Terraform GitLab Provider
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...
For a given Project, it would be super helpful to have a Data source for a Repository and it's (Container) Registry - this for example can help with retreiving branches,...
## Description Looking at our test code, we have a number of different testing approaches that vary by resource. 😩 As long as new PRs are looking to existing testing...
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...
### Terraform Version Terraform v0.14.5 ### Affected Resource(s) - gitlab_service_jira ### Terraform Configuration Files ```hcl resource "gitlab_service_jira" "my_project" { project = gitlab_project.my_project.id url = "https://myjiraserver.tld" username = "user" password =...