A customer flagged Terraform state drift on tagged buckets last Thursday. The symptom rang a bell, we'd seen something like it in February, but I couldn't find the ticket. Linear's search returned six pages with "terraform" in the title and none of them obviously matched. The closest hit was an Annie investigation report attached as a comment two months ago, not the parent ticket. I gave up after forty minutes and asked Jean, who pointed me at the right project, which I would not have guessed.

This morning, with the Linear integration GA, I asked Annie the same question.

Twenty-three seconds.

She returned BACK-512, "Terraform state import drifts on tagged buckets," filed by Roxane on 2026-02-14, with the linked PR (anyshift-backend#1881) that landed half the fix, and the two-line tail of the description noting the second half was punted to next quarter. She also surfaced the comment thread where Jean flagged the same drift pattern returning three weeks after the partial fix. The current customer report is the second recurrence, not the first.

Have we seen this Terraform tag drift before?
louis.fradin · May 13, 2026, 05:13 PM
Customer flagged tagged-bucket drift on Terraform import. Did we see this before?
May 13, 2026, 05:13 PM · Thought for 23 seconds

Found it. Roxane's February ticket, same drift pattern:

BACK-512
Terraform state import drifts on tagged buckets
Done · partial2026-02-14Roxane Fischer

From the description, tail two lines:

Tag-mutation race on aws_s3_bucket.tags import causes plan diff on every run.
Provider fix lands v0.42. Backend side punted to Q3, see comment thread.

Linked PR, half the fix:

anyshift-backend#1881 · Patch tag-mutation race on bucket import
Merged 2026-02-21 · +84 / −12 · provider bump only, backend retry path deferred

Comment thread, three weeks after the partial fix:

JD
Jean Dupontcommented · 2026-03-13
“Drift pattern is back on cust-prod-eu-west-1. Same signature as the original. Provider bump alone isn't sufficient under concurrent imports.”
Current customer report is the second recurrence, not the first.

Would you like me to:

  • · Re-open BACK-512 with the customer report attached?
  • · Pull every tagged-bucket import drift across customer Terraform Cloud workspaces?
  • · Open a new Linear ticket for the deferred backend retry path?
Your chats aren't used to train models.

The hardest thing to find in a ticket tracker is the right ticket

Linear's search is fine for titles and exact strings. It is bad at body-text recall, particularly for the kind of half-remembered detail you actually need ("the one where the import drifted but only on tagged resources"). I'd searched the producer team's project when the original ticket had been filed against the consumer team. Annie picked it off the body, without me knowing where to look.

The next time Linear ships an integration feature, Annie has it without us touching agent-gateway. We built the credential bridge once.

Setup: docs.anyshift.io/integration/linear