Jon Chery
c80060878a
EXECUTE stage. Authors the remaining 11 L1 module terraform subdirs with the full versions/variables/locals/main/outputs split. Defaults previously hardcoded in the adapter move into locals.tf. Simple single-resource modules (7): - kms-key: aws_kms_key + alias (enable_key_rotation, deletion_window defaults) - ecr: aws_ecr_repository (encryption_configuration from kms_key_arn, image_scanning) - ecs-cluster: aws_ecs_cluster (name default) - iam-role: aws_iam_role + inline_policy (assume_role_policy fallback, ECR/logs policy in locals.tf) - rds: aws_db_instance (storage_encrypted, multi_az, kms_key_arn defaults) - waf: aws_wafv2_web_acl (default_action, visibility_config, dynamic rules) - uptime: aws_ecs_task_definition + aws_ecs_service (Fargate compat, container_definitions in locals.tf) Multi-resource modules with intra-refs (4): - vpc: aws_vpc + aws_subnet + aws_internet_gateway + aws_route_table (CIDR derivation in locals.tf) - ecs-service: aws_ecs_task_definition + aws_ecs_service (Fargate compat, container_definitions, network_config in locals.tf) - alb: aws_lb + aws_lb_target_group + aws_lb_listener (subnet/security_group list derivation in locals.tf) - cloudfront: aws_cloudfront_distribution + aws_cloudfront_origin_access_control (OAC defaults in locals.tf) Registry: terraform_dir added to all 11 remaining entries. Adapter fix: stack output format uses separate 'from' + 'output' fields (not 'from': 'rid.output'). Fixed _emit_root_output to read both fields. 6 previously-skipped tests unblocked (run_platform.sh --check-only now resolves static-assets.yml through the new module-assembled adapter). Removed skip markers. Fixed test assertion (aws_s3_bucket → module). Regression: 461 passed, 0 skipped, 5 deselected (slow). All 12 modules pass run_primitive_plan.sh --check-only. All 12 terraform/ subdirs pass terraform init + validate standalone. ---ci--- project: acdl phase: P56b milestone: v1.11 status: execute ---/ci---
ecr — ECR repository
Module kind: primitive | Version: 1.0.0
A single ECR repository that hosts the container image for the ECS task. The simplest container-registry module — one resource, two inputs, two outputs.
Resources
| Resource | Type | Purpose |
|---|---|---|
| repository | aws_ecr_repository |
The ECR repository |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | The ECR repository name |
region |
string | yes | — | AWS region the repository is created in |
Outputs
| Name | Type | Description |
|---|---|---|
repository_url |
string | The ECR repository URL |
repository_arn |
arn | The ECR repository ARN |
Usage
{
"id": "ecr",
"type": "aws:ecr:repository",
"module": "ecr@1.0.0",
"inputs": {
"name": "acdl-microservice",
"region": "us-east-1"
}
}
The repository_url output is used to build the image input for
ecs-service (e.g. <repository_url>:latest).
Compliance extension points
- Image scanning — add
image_scanning_configuration { scan_on_push = true }for vulnerability scanning (SOC2 CC7.6, DORA ICT risk testing, security monitoring). - Encryption — add
encryption_configuration { encryption_type = "KMS", kms_key = ... }with a customer-managed key (SOC2 CC6.1, GDPR Art.32). - Image tag immutability — add
image_tag_mutability = "IMMUTABLE"to prevent tag overwriting (SOX §802, SOC2 CC6.1 integrity, DORA audit integrity). - Lifecycle policy — add
aws_ecr_lifecycle_policyto enforce image retention / cleanup (GDPR Art.5(2) data minimization, SOC2 CC5.2). - Access policy — add a repository policy restricting pull/push to known roles (SOC2 CC6.1.
Examples
Validated example contracts are in examples/. The platform-test
pipeline validates them against schemas/contract.schema.json.
Simple
A minimal deployment:
environment: dev
id: ecr
infrastructure:
ecr:
inputs:
name: my-repo
region: us-east-1
version: 1.0.0
name: ecr-repo
Complex
A production deployment with optional inputs:
environment: dev
id: ecr
infrastructure:
ecr:
inputs:
name: my-production-repo
region: us-east-1
version: 1.0.0
name: ecr-repo
Versioning
1.0.0 — interface MAJOR, behavior MINOR, lifecycle PATCH. MAJOR bumps
require a new registry entry (immutable publication); old entries enter
a 12-month deprecation window.