From 085ac3e66a7cecd3309af2cf331ea51a91280a8e Mon Sep 17 00:00:00 2001 From: Lauri Date: Fri, 1 Sep 2023 17:47:27 +0200 Subject: [PATCH] Adds troubleshooting section --- website/docs/terraform/get-started-terraform.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/docs/terraform/get-started-terraform.mdx b/website/docs/terraform/get-started-terraform.mdx index e930b1d69e..390473ab2e 100644 --- a/website/docs/terraform/get-started-terraform.mdx +++ b/website/docs/terraform/get-started-terraform.mdx @@ -165,6 +165,12 @@ spec: For a full list of features and how to use them, please visit the [Terraform overview](../terraform-intro). +### Troubleshooting + +#### Getting a `drift detected` event message when it's a change of source that triggered the update + +Whenever you change a source, you will get a new plan. TF-controller picks up the new plan and applies it. Drift happens if, and only if, the live system changes intentionally. Then TF-controller will generate a lengthy message [see an example](https://github.com/weaveworks/tf-controller/issues/890#issuecomment-1691610117) stating that a drift has occurred. If there is drift, the icon will be red in the TF Objects > Status column of the WGE UI. + ## Other Examples * A Terraform GitOps with Flux to automatically reconcile your [AWS IAM Policies](https://github.com/tf-controller/aws-iam-policies). * GitOps an existing EKS cluster by partially importing its nodegroup and managing it with TF-controller: [An EKS scaling example](https://github.com/tf-controller/eks-scaling).