Skip to content
terragucciDocs

Drift

llms.txtlists every page for an agent
Optional: hand this page to your coding agentThe steps work by hand too.
Show the whole prompt
Read https://intentius.io/terragucci/tutorial/drift/.
In the terragucci clone with the example booted, run the `just example` commands on the page. Summarize what the drift issue names, and where it differs from the page.
Never apply, approve (a pull request review or `terragucci approve`), override a policy denial (`terragucci override`), use `--mode apply`, or merge; never touch `.chant/allowed_signers` or `chant/lifecycle`.

Someone deletes a queue in the console.

  1. The scenario deletes it through the API.

    $ just example change drift
deleted shop-staging-orders-jobs from floci, outside Terraform

  2. Run the drift job by hand from the Actions tab, or wait for six in the morning. Its -refresh-only plan of every root compares state with what exists in floci and never reads the code, so a change waiting on main is not drift. The report lists the deleted queue under deletes, in envs/staging/orders as module.service.aws_sqs_queue.jobs.

  3. Open the issue the job opened, terragucci: drift found. It names envs/staging/orders and the queue shop-staging-orders-jobs. A second run updates it.

    The drift issue in Forgejo, naming envs/staging/orders and its deleted queue shop-staging-orders-jobsThe drift issue in Forgejo, naming envs/staging/orders and its deleted queue shop-staging-orders-jobs

Applying the code recreates the queue, which just example reset does. The next drift run then closes the issue on AWS; on floci the tag entries keep it open.

Tutorial step 6 of 11.

terragucci

These docs count page views and clicks with PostHog. They set no cookies, store nothing in your browser, and send nothing when your browser asks not to be tracked.