opentofu-module

Standardize infrastructure deployment with versioned OpenTofu modules and OPA-gated CI pipelines.

1|Updated Jun 20, 2026

Search Tags:#automation #compliance #platform #cloud #infrastructure #iac #opentofu

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill opentofu-module

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opentofu-module
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/opentofu-module
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill opentofu-module

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates infrastructure drift and manual configuration errors by enforcing a standardized, versioned, and OPA-gated OpenTofu workflow for all cloud resources.

Core Features & Use Cases

Golden Path Provisioning: Enables developers to request infrastructure via simple YAML templates, removing the need for them to write HCL.
Automated Compliance: Integrates OPA policy checks into the CI pipeline to ensure all infrastructure meets security and residency requirements before deployment.
Multi-Tenant Isolation: Implements a directory-per-tenant model with shared modules, ensuring strict isolation and simplified version upgrades across the fleet.

Quick Start

Use the opentofu-module skill to generate a new infrastructure request for a postgresql database in the staging environment for the specified tenant.

Frequently Asked Questions about opentofu-module

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize OpenTofu modules across multi-tenant cloud environments?▼

Standardize OpenTofu modules across multi-tenant cloud environments by enforcing strict state isolation with a directory-per-tenant model and shared versioned modules. This ensures consistent resource configuration across AWS, Azure, and GCP while maintaining strict isolation.

Can I enforce OPA compliance gates in an OpenTofu CI pipeline?▼

Yes, you can enforce OPA compliance gates in an OpenTofu CI pipeline. Integrating OPA policy checks ensures all infrastructure meets security and residency requirements automatically before any deployment occurs.

How do I enable self-service infrastructure provisioning without writing HCL?▼

Enable self-service infrastructure provisioning by allowing developers to request resources via simple YAML templates. This golden path approach removes the need for developers to write HCL directly.

What is the best way to prevent infrastructure drift in versioned OpenTofu workflows?▼

The best way to prevent infrastructure drift in versioned OpenTofu workflows is to enforce a standardized, OPA-gated pipeline for all cloud resources. This eliminates manual configuration errors and maintains stable interfaces.

Does OpenTofu automated provisioning support secure credential handling across AWS, Azure, and GCP?▼

Yes, OpenTofu automated provisioning supports secure credential handling across AWS, Azure, and GCP. The standardized workflow ensures consistent resource configuration while maintaining secure credential handling across all providers.

When should I not use a standardized OpenTofu module workflow?▼

You should not use a standardized OpenTofu module workflow if your team requires ad-hoc, non-compliant infrastructure changes outside of CI pipelines. This approach enforces strict OPA compliance gates and standardization, which prevents untracked manual configurations.