gitlab_group_service_account_access_token produced inconsistent result after apply

Bug Report

When rotating the token, the provider produces an inconsistent result.

Relevant Terraform Configuration

resource "gitlab_group_service_account_access_token" "mirror_setup_write_token" {
  group   = data.gitlab_group.top_level_group.id
  user_id = local.main_service_account_id
  name    = "Mirror setup token (write)"

  scopes = ["api"]

  rotation_configuration = {
    rotate_before_days = 14
    expiration_days    = 30
  }
}

https://gitlab.com/gitlab-community/meta/-/blob/4a54d72036dee61010e6f6ee977dc2c235f1989f/tofu/states/provider_tokens/main.tf#L23-34

Relevant Terraform Command

tofu apply

Relevant Log Output

╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ gitlab_group_service_account_access_token.mirror_setup_write_token,
│ provider "provider[\"registry.opentofu.org/gitlabhq/gitlab\"]" produced an
│ unexpected new value: .validate_past_expiration_date: was null, but now
│ cty.False.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵

https://gitlab.com/gitlab-community/meta/-/jobs/12562453090

Additional Details

  • GitLab Terraform Provider Version: v18.7.0
  • GitLab Instance Version: 18.8.0-pre 4504cfd4294
  • Terraform Version: gitlab-opentofu:3.7.0-opentofu1.10.6-alpine
  • License Tier: Ultimate (OSS)
Edited Dec 29, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading