90be5839ab
Phase 26 — platform-pipelines-and-release-automation: - platform-test.yml: PR pipeline (lint + unit-test + integration-test + schema-validation) replacing ci.yml for PRs; integration-test runs run_platform.sh --check-only for every contracts/*.yaml - primitives-plan.yml: PR pipeline with matrix over all 9 L1 primitives (s3, vpc, ecs-cluster, ecs-service, iam-role, alb, ecr, cloudfront, waf) - patterns-plan.yml: PR pipeline with matrix over all 2 L2 modules (static-assets, microservice) - release.yml: push-to-main pipeline computing next semver tag (PATCH for regular phases, MINOR for milestone completions), updating floating MAJOR.MINOR + MAJOR tags, and creating GitHub releases - run_primitive_plan.sh: plan-only/check-only runner for a single L1 primitive (adapter compile + structure validation offline) - run_pattern_plan.sh: plan-only/check-only runner for a single L2 pattern (environment check + contract validate + resolve + adapter + structure validation offline) - contracts/microservice.yaml: sample consumer contract for the microservice L2 module (schema-compliant scalar inputs) - instance.json for 8 L1 primitives (vpc, ecs-cluster, ecs-service, iam-role, alb, ecr, cloudfront, waf) so the primitives-plan matrix can run the adapter offline; s3 already had one - tests/test_release_logic.py: unit test for semver computation (PATCH bump, MINOR bump on milestone, floating tag format) - tests/test_pipeline_contract.py: 19 new tests validating the 4 platform workflows exist and conform (stages, matrices, triggers, permissions) DEVIATION: The microservice pattern (run_pattern_plan.sh --check-only microservice + run_platform.sh --check-only contracts/microservice.yaml) fails at the adapter stage due to a pre-existing resolver ref-id mismatch for multi-resource L1s (resolver emits ref:vpc.subnet_ids but the expanded resource id is vpc-subnet). This predates Phase 26 and is out of scope for pipeline automation; the static-assets pattern passes end-to-end. The microservice contract is schema-valid and resolves correctly (11 resources); only the adapter compilation of multi-resource L1 refs fails. VERIFICATION: - bash scripts/run_ci.sh: PASS (lint + test + check-only) - python3 -m pytest tests/ -v: 266 passed - bash scripts/run_primitive_plan.sh --check-only s3: PASS - bash scripts/run_pattern_plan.sh --check-only static-assets: PASS - All 9 primitives pass run_primitive_plan.sh --check-only - All instance.json validate against stack.schema.json ---ci--- project: acdl phase: 26 milestone: v1.7 status: execute ---/ci---
alb — Application Load Balancer (load balancer + target group + listener)
Module kind: primitive | Version: 1.0.0
An Application Load Balancer with a target group and a listener. This is
a multi-resource module: it creates a load balancer, a target group, and
a listener that forwards traffic to the target group. The target group
is what ecs-service registers its tasks with.
Resources
| Resource | Type | Purpose |
|---|---|---|
| load_balancer | aws_lb |
Application load balancer in the VPC subnets |
| target_group | aws_lb_target_group |
Target group for the ECS service tasks |
| listener | aws_lb_listener |
Listener forwarding the LB port to the target group |
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
name |
string | yes | — | Name tag for the load balancer and child resources |
subnets |
string | yes | — | Comma-separated subnet ids (from vpc) |
security_group |
string | yes | — | Security group id for the load balancer |
port |
number | no | 80 | Listener port |
protocol |
string | no | HTTP |
Listener protocol |
region |
string | yes | — | AWS region the load balancer is created in |
Outputs
| Name | Type | Description |
|---|---|---|
lb_arn |
arn | The load balancer ARN |
listener_arn |
arn | The listener ARN |
target_group_arn |
arn | The target group ARN |
Usage
{
"id": "alb",
"type": "aws:elbv2:loadbalancer",
"module": "alb@1.0.0",
"inputs": {
"name": "acdl-microservice",
"subnets": "ref:vpc.subnet_ids",
"security_group": "ref:roles.role_arn",
"port": 8080,
"protocol": "HTTP",
"region": "us-east-1"
}
}
The target_group_arn output is referenced by ecs-service as its
lb_target_group_arn input to wire the service to the ALB.
Compliance extension points
- TLS / HTTPS listener — add
aws_acm_certificate+ssl_policy+certificate_arnfor encryption in transit (SOC2 CC6.1, PCI-DSS 4.1, HIPAA §164.312(e)(1), GDPR Art.32). - Access logs — add
access_logs { bucket = ..., prefix = ... }to the load balancer (SOX, SOC2 CC7.2, DORA ICT audit trail). - Security group rules — add ingress/egress rules restricting traffic to known sources (SOC2 CC6.6, PCI-DSS 1.2).
- Health check — add a
health_checkblock to the target group (SOC2 CC7.3 monitoring, DORA operational resilience). - WAF — add
aws_wafv2_web_acl_associationfor application-layer protection (SOC2 CC7.6, PCI-DSS 6.5, DORA ICT risk). - Deregistration delay — add
deregistration_delayfor graceful draining (SOC2 CC9.1 resilience).
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.