Tags: zapier/tfbuddy
Tags
fix: attach pipeline ID to GitLab commit status updates (#65) The closure in updateStatus used to assign the resolved pipeline ID, shadowing the outer variable and discarding the value. Every SetCommitStatus call was issued without a PipelineID, so GitLab couldn't associate the status with the current MR pipeline — leaving the apply check stuck after no-change plan/applies and causing pipeline-status links to point at stale runs. Signed-off-by: Mmadu Manasseh <mmadumanasseh@gmail.com>
CLOUD-933 Fix stale workspace lock cleanup and add auto-recovery (#56) * Fix stale workspace lock cleanup and add auto-recovery The TriggerCleanupEvent loop would crash (nil pointer dereference) when any workspace in .tfbuddy.yaml no longer exists in TFC, preventing lock cleanup for all remaining workspaces. This caused stale tfbuddylock-* tags to accumulate, blocking new applies even after the locking MR was merged. - Add continue after workspace/tag lookup errors in cleanup loop so one missing workspace doesn't break cleanup for the rest - Add stale lock auto-recovery: when a workspace is locked by another MR, check if that MR is merged/closed and auto-clean the tag - Update tfc unlock to also remove tfbuddylock-* tags, giving users a way to manually clear stale tag locks - Add GetState() to DetailedMR interface for MR state inspection Signed-off-by: Ihor Horak <ihor.horak@zapier.com>
PreviousNext