CtrlK
BlogDocsLog inGet started
Tessl Logo

guidion-digital/terraform-modules

Standards and workflows for building secure, well-structured Terraform modules, including planning gates, validation steps, and implementation guidance.

82

1.77x
Quality

84%

Does it follow best practices?

Impact

80%

1.77x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-2/

Record Completed Terraform Module Work

Problem/Feature Description

Your team maintains a Terraform module library for internal AWS infrastructure. A senior engineer has just finished a cleanup task on the modules/iam module: they replaced inline JSON strings in aws_iam_policy resources with aws_iam_policy_document data sources, making the policies easier to read and maintain. As part of this, they also updated the module's README.md to document the new data source approach.

The work is complete. Terraform fmt, validate, and plan all passed (exit code 0, no diff — this was a pure refactor that should not change any infrastructure). No gates were waived. The AWS account used for testing was 123456789012 (staging) and the IAM role ARN was arn:aws:iam::123456789012:role/ci-terraform-role — these are internal values that should not appear in documentation.

Your job is to record this completed work so the team has a clear audit trail of what changed, why, and that it was validated.

Output Specification

Create the task log record for this work. The log should be a markdown file placed in the correct location within the repository, named according to the team's conventions.

Output file: the task log markdown file at its correct path.

tile.json