Skip to content

Ignore ever-changing next_run_at in container expiration policy in forks

Timo Furrerrequested to merge
container-expiration-next-run-ignore into main

The container_expiration_policy.next_run_at attribute keeps changing, because GitLab updates it every now and then. We'd see this as drifts like:

OpenTofu detected the following changes made outside of OpenTofu since the
last "tofu apply" which may have affected this plan:
 # gitlab_project.forks["gitlab-org/build/CNG"] has changed
 ~ resource "gitlab_project" "forks" {
 id = "55226044"
 name = "CNG"
 tags = []
 # (85 unchanged attributes hidden)
 ~ container_expiration_policy {
 ~ next_run_at = "2025-10-09T02:17:00Z" -> "2025-10-10T03:16:30Z"
 # (6 unchanged attributes hidden)
 }
 # (1 unchanged block hidden)
 }

Example: https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot/-/jobs/11657615075

This change set ignores changes to that attribute.

Merge request reports