[PR #349] [MERGED] Add tf-why: Terraform drift attribution via CloudTrail #4633

New Issue

GiteaMirror · 2026-06-01T05:37:08-05:00

GiteaMirror commented

2026-06-01 05:37:08 -05:00

📋 Pull Request Information

Original PR: https://github.com/shuaibiyy/awesome-tf/pull/349
Author: @Raj-glitch-max
Created: 5/4/2026
Status: ✅ Merged
Merged: 5/4/2026
Merged by: @antonbabenko

Base: master ← Head: main

📝 Commits (1)

58031e7 Add tf-why: Terraform drift attribution via CloudTrail

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Hi! I'm nominating tf-why, a CLI tool that helps platform engineers identify who caused infrastructure drift.

Terraform tells you what drifted, but finding the root cause usually involves hunting through CloudTrail logs. tf-why automates this by correlating Terraform plan JSON with CloudTrail events to attribute the change to a specific AWS actor, timestamp, and API event.

Key features:

Correlates terraform plan output with CloudTrail.
Attributes changes to specific IAM Users, Roles, or SSO identities.
Non-invasive (read-only access).
JSON and Plain text output for CI/CD integration.
Repo: https://github.com/Raj-glitch-max/tf.why

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/shuaibiyy/awesome-tf/pull/349 **Author:** [@Raj-glitch-max](https://github.com/Raj-glitch-max) **Created:** 5/4/2026 **Status:** ✅ Merged **Merged:** 5/4/2026 **Merged by:** [@antonbabenko](https://github.com/antonbabenko) **Base:** `master` ← **Head:** `main` --- ### 📝 Commits (1) - [`58031e7`](https://github.com/shuaibiyy/awesome-tf/commit/58031e78f15c19664d368f1b67070dc38c80ff82) Add tf-why: Terraform drift attribution via CloudTrail ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Hi! I'm nominating tf-why, a CLI tool that helps platform engineers identify who caused infrastructure drift. Terraform tells you what drifted, but finding the root cause usually involves hunting through CloudTrail logs. tf-why automates this by correlating Terraform plan JSON with CloudTrail events to attribute the change to a specific AWS actor, timestamp, and API event. Key features: Correlates terraform plan output with CloudTrail. Attributes changes to specific IAM Users, Roles, or SSO identities. Non-invasive (read-only access). JSON and Plain text output for CI/CD integration. Repo: https://github.com/Raj-glitch-max/tf.why --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-01 05:37:08 -05:00

GiteaMirror closed this issue

2026-06-01 05:37:10 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-tf#4633