gitlab_user_runner fails on update if maximum_timeout was not set explicitly
Bug Report
When deploying a gitlab_user_runner
resource without maximum_timeout
set explicitly, the value is set to 0
within the terraform state.
If this resource is getting updated (e.g. Description or Tags changed) the update fails with the following error:
╷
│ Error: Error updating GitLab runner
│
│ with gitlab_user_runner.runner,
│ 1: resource "gitlab_user_runner" "runner" {
│
│ Error updating GitLab runner <ID>: PUT
│ https://<URL>/api/v4/runners/<ID>: 400 {message:
│ {maximum_timeout: [needs to be at least 10 minutes]}}
╵
Relevant Terraform Configuration
resource "gitlab_user_runner" "runner" {
runner_type = "group_type"
description = "foo"
group_id = <ID>
tag_list = ["foo", "bar"]
}
# when updating any property (e.g. tag_list = ["foo", "bar2"]) the issue occurs.
Relevant Terraform Command
terraform ...
Relevant Log Output
These are the debug logs of the `terraform` command output:
Additional Details
- GitLab Terraform Provider Version:
16.5.0
- GitLab Version:
16.1.5
- Terraform Version:
v1.6.3