feat: Add OCI awareness across agents and skills

Adds awareness of Oracle Cloud Infrastructure to any plugin that referenced
at least two of the major cloud vendors already. Skills updated to include
OCI services. Also updated some of the other cloud references.

Signed-off-by: Avi Miller <me@dje.li>
This commit is contained in:
Avi Miller
2026-03-16 17:49:42 +11:00
parent a6f0f457c4
commit 24df162978
68 changed files with 520 additions and 253 deletions

View File

@@ -1,11 +1,11 @@
---
name: terraform-module-library
description: Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
description: Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
---
# Terraform Module Library
Production-ready Terraform module patterns for AWS, Azure, and GCP infrastructure.
Production-ready Terraform module patterns for AWS, Azure, GCP, and OCI infrastructure.
## Purpose
@@ -32,10 +32,14 @@ terraform-modules/
│ ├── vnet/
│ ├── aks/
│ └── storage/
── gcp/
├── vpc/
├── gke/
└── cloud-sql/
── gcp/
├── vpc/
├── gke/
└── cloud-sql/
└── oci/
├── vcn/
├── oke/
└── object-storage/
```
## Standard Module Pattern
@@ -174,6 +178,8 @@ output "vpc_cidr_block" {
9. **Test modules** with Terratest
10. **Tag all resources** consistently
**Reference:** See `references/aws-modules.md` and `references/oci-modules.md`
## Module Composition
```hcl

View File

@@ -58,7 +58,7 @@
## Best Practices
1. Use AWS provider version ~> 5.0
1. Use AWS provider version `~> 6.31`
2. Enable encryption by default
3. Use least-privilege IAM
4. Tag all resources consistently

View File

@@ -0,0 +1,52 @@
# OCI Terraform Module Patterns
## VCN Module
- VCN with public/private subnets
- Dynamic Routing Gateway (DRG) attachments
- Internet Gateway, NAT Gateway, Service Gateway
- Route tables and security lists / NSGs
- VCN Flow Logs
## OKE Module
- OKE cluster and node pools
- IAM policies and dynamic groups
- VCN-native pod networking
- Cluster autoscaling and observability hooks
- OCIR integration
## Autonomous Database Module
- Autonomous Database provisioning
- Network access controls and private endpoints
- Wallet and secret handling
- Backup and maintenance preferences
- Tagging and cost tracking
## Object Storage Module
- Buckets with lifecycle rules
- Versioning and retention
- Customer-managed encryption keys
- Replication policies
- Event rules and service connectors
## Load Balancer Module
- Public or private load balancer
- Backend sets and listeners
- TLS certificates
- Health checks
- Logging and metrics integration
## Best Practices
1. Use the OCI provider version `~> 7.26`
2. Model compartments explicitly and pass them through module interfaces
3. Prefer NSGs over broad security list rules where practical
4. Tag all resources with owner, environment, and cost center metadata
5. Use dynamic groups and least-privilege IAM policies for workload access
6. Keep network, identity, and data modules loosely coupled
7. Expose OCIDs and subnet details for module composition
8. Enable logging, metrics, and backup settings by default