continuous-intelligence/acdl

Fork 0

Files

T

History

Jon Chery 4dad967910

acdl-ci / Lint (pull_request) Successful in 7s

Details

acdl-ci / Platform check-only (offline) (pull_request) Successful in 21s

Details

acdl-modules-lifecycle / CI VPC apply (pull_request) Successful in 39s

Details

acdl-ci / Test (pull_request) Successful in 4m18s

Details

acdl-modules-lifecycle / L1 lifecycle (alb) (pull_request) Failing after 1m4s

Details

acdl-modules-lifecycle / L1 lifecycle (cloudfront) (pull_request) Successful in 8m51s

Details

acdl-modules-lifecycle / L1 lifecycle (ecr) (pull_request) Successful in 2m37s

Details

acdl-modules-lifecycle / L1 lifecycle (ecs-cluster) (pull_request) Successful in 3m0s

Details

acdl-modules-lifecycle / L1 lifecycle (iam-role) (pull_request) Successful in 2m43s

Details

acdl-modules-lifecycle / L1 lifecycle (ecs-service) (pull_request) Successful in 4m4s

Details

acdl-modules-lifecycle / L1 lifecycle (kms-key) (pull_request) Successful in 2m53s

Details

acdl-modules-lifecycle / L1 lifecycle (s3) (pull_request) Successful in 2m48s

Details

acdl-modules-lifecycle / L1 lifecycle (uptime) (pull_request) Successful in 3m45s

Details

acdl-modules-lifecycle / L1 lifecycle (vpc) (pull_request) Successful in 2m46s

Details

acdl-modules-lifecycle / L1 lifecycle (waf) (pull_request) Successful in 3m8s

Details

acdl-modules-lifecycle / L2 lifecycle (microservice) (pull_request) Failing after 54s

Details

acdl-modules-lifecycle / L2 lifecycle (static-assets) (pull_request) Failing after 55s

Details

acdl-modules-lifecycle / L1 lifecycle (rds) (pull_request) Successful in 32m32s

Details

acdl-modules-lifecycle / CI VPC destroy (pull_request) Failing after 20m33s

Details

fix(P60): ALB target group name_prefix — avoid orphaned resource conflicts

The ALB lifecycle test was failing with "ELBv2 Target Group (acdl-ci-alb)
already exists" because a prior failed run left an orphaned target group
in AWS. The deterministic state key means terraform reuses the same state,
but create_before_destroy tries to create a new target group with the same
name before destroying the old one → conflict.

Fix: use name_prefix instead of name for the target group. AWS auto-generates
a unique name (e.g. acdl-ci-alb-2026072812001234567), so create_before_destroy
can create the new target group without conflicting with the orphaned one.
The old orphaned target group is eventually garbage-collected by AWS (or
cleaned up by a future run's destroy step).

This is the standard terraform pattern for create_before_destroy resources
with name uniqueness constraints.

---ci---
project: acdl
phase: P60
milestone: v1.11
status: execute
---/ci---

2026-07-28 20:22:41 +00:00

fix(P60): ALB target group name_prefix — avoid orphaned resource conflicts

2026-07-28 20:22:41 +00:00

feat(P61): L2 lifecycle pipeline — extend matrix + workflows + tests

2026-07-28 20:17:27 +00:00

.gitkeep

docs(P20): specify phase 20 — consumer happy path + reusable deploy workflow (v1.5)

2026-07-22 17:09:23 +00:00

README-TEMPLATE.md

docs(P47): presentation slide updates + HIPAA removal from all docs

2026-07-23 14:08:40 +00:00

README.md

docs(P48): vision gaps + badge system + substrate→engine + CR format + agentic tags

2026-07-23 14:58:29 +00:00

registry.json

feat(P56b): author 11 L1 module terraform subdirs + fix adapter output format

2026-07-28 16:07:57 +00:00

STANDARDS.md

feat(P56a): stateless adapter rewrite + s3 reference terraform module

2026-07-28 16:07:57 +00:00

README.md

ACDL Modules

Reusable building blocks for cloud infrastructure. Each module is self-documented with a README.md following the template.

How the modules work

There are two kinds of module:

Primitives — a single cloud resource or a small group of related resources (e.g. a VPC with subnets and routing). Each primitive has an interface.json declaring its inputs and outputs, and a README.md in plain language.
Modules — a pattern that references multiple primitives to deploy a complete stack (e.g. an ECS Fargate microservice). Each module has a composition.json declaring its children and wires.

The engine adapter (adapters/terraform/adapter.py) compiles a module instance to infrastructure. Each module's README documents which resources it creates.

Primitives

Module	What it creates	README
`s3`	`aws_s3_bucket` — a single S3 bucket	README
`vpc`	`aws_vpc` + `aws_subnet` + `aws_route_table` + `aws_internet_gateway` — VPC with subnets and routing	README
`ecs-cluster`	`aws_ecs_cluster` — ECS Fargate cluster	README
`ecs-service`	`aws_ecs_task_definition` + `aws_ecs_service` — Fargate service with task definition	README
`iam-role`	`aws_iam_role` — IAM role with assume-role policy	README
`alb`	`aws_lb` + `aws_lb_target_group` + `aws_lb_listener` — Application Load Balancer	README
`ecr`	`aws_ecr_repository` — ECR container image repository	README
`cloudfront`	`aws_cloudfront_distribution` + `aws_cloudfront_origin_access_control` — CloudFront distribution with S3 origin via OAC	README
`waf`	`aws_wafv2_web_acl` — WAFv2 Web ACL (CloudFront-scoped)	README
`rds`	`aws_db_instance` — Relational database (PostgreSQL, MySQL, etc.) with multi-engine support	README
`kms-key`	`aws_kms_key` — Customer-managed KMS key with rotation enabled (per-stack CMK)	README
`uptime`	`aws_ecs_service` — Uptime-kuma monitoring on ECS Fargate with alert channels	README

Modules

Module	What it references	README
`microservice`	6 primitives (vpc, cluster, ecr, iam-role, alb, ecs-service)	README
`static-assets`	3 primitives (s3, cloudfront, waf)	README

Registry

Module versions are tracked in registry.json. Both primitives and modules are registered.

Template

New modules should use README-TEMPLATE.md as their starting point.

Module patterns (roadmap)

The current composition.json mechanism is a thin pattern layer. A future redesign will let a consumer dynamically create a module directly from the contract file (an agentic "composition" flow). That is on the roadmap, not implemented today.