rootsami / terradrift Goto Github PK

Currently if terraform version is not defined in tf files, it throws an error.

ERRO[0000] no problems                                   stack=gcp-core-staging
ERRO[0000] running NewTerraform: no suitable terraform binary could be found: NewTerraform: please supply the path to a Terraform executable using execPath, e.g. using the github.com/hashicorp/hc-install module.  stack=gcp-core-staging

How to reproduce it:
remove the block and run terradrift against the example stacks

Possible Actions:

• Enhance error handling to show what's actually wrong.
• Validation if terraform version is not defined.
• Defaulting to the latest version is possible, however, it might cause an issue for the user by upgrading the remote state which is out of terradrift scoop by running terraform init with a later tf version

Description

if a stack drift scan fails to run for any reason, it fails silently and only reports in the logs

Possible Actions:

Add metrics for stack failure to be able to monitor failures.
Type: gauge
Unit: bool
Description: Has a value of 1 when failure is detected, and 0 when it's not.

Example:

# HELP terradrift_plan_failure Status of the latest scan run
# TYPE terradrift_plan_failure gauge
terradrift_plan_failure{stack="api-staging"} 0

I think the variable REPOISTORY should be REPOSITORY. 😉

Seem like it could look for an atlantis.yaml in the git repo's root folder and build a stack config from that if it found it.

Current drift calculations are happening based on the human-readable plan output.

Plan: 0 to add, 0 to change, 4 to destroy.

It needs to be calculated in a programmatical way using terraform show -json <PLAN FILE> to avoid any possible changes in the future versions of terraform
References: https://developer.hashicorp.com/terraform/internals/json-format#plan-representation

I could be missing something but it appears from the examples that there is no S3 backend support. Is that the case?

I feel it's a common use case and would be a great addition here.
There is really not any competition in this area besides driftctl and it's a fantastic area to improve on Terraform.

Getting the following error when I run terradrift-cli

OS: MacOS 13.2 - M1

terraform path:

which terraform
/opt/homebrew/bin/terraform

terradrift-cli --workdir="./stacks"

ERRO[0000] running NewTerraform: no suitable terraform binary could be found: NewTerraform: please supply the path to a Terraform executable using execPath, e.g. using the github.com/hashicorp/hc-install module.