[New Process Improvement Proposal]: Standardize Terraform Module Library Aligned with SLIM Best Practices

Checked for duplicates

No - I haven't checked

Category

Software Lifecycle - the creation, change, and release of software

Describe the need

With the increasing adoption of Terraform across JPL teams, there's a growing need to standardize IaC (infrastructure-as-code) practices to promote reusability, maintainability, and consistency. I am proposing a centralized Terraform repo that aligns fully with SLIM best practices (modular design, input validation, CI checks, versioning, and documentation).

This will help promote code reuse across multiple JPL projects, ensure infra deployments follow SLIM-aligned best practices, and enable safer deployments via standardized validations and CI integrations (workflows).

Next Steps:

1. Align with SLIM team on priority and scope.
2. Determine repo ownership and permissions.
3. Start with handful of high-impact modules (e.g. VPC, S3, IAM roles, RDS, ECS)

Start by aligning with the SLIM team on the proposal's priority and scope; the issue names no files, tests, or entry points. Determine repo ownership and permissions, then define the initial high-impact modules, such as VPC, S3, IAM roles, RDS, and ECS. Done means an agreed scope, ownership model, and prioritized starting set.