 Jon Chery
|
699aa542df
|
docs(P15): plan-as-execute + verify (v1.2.5, PARTIAL — terraform apply blocked by IAM)
---ci---
project: acdl
phase: 15
milestone: v1.2
status: verify
verdict: PARTIAL
requirements:
covered: [REQ-34]
partial: [REQ-33]
blocker:
- id: P0-IAM
description: terraform apply fails with AccessDenied on ECS/ECR/IAM/EC2 — live spike_runner_policy.json not pushed (root key deactivated per D-034)
unblock: operator runs create_iam_user.py with root/admin creds to push the expanded policy, then terraform apply succeeds (plan valid, 13 to add)
---/ci---
Phase 15 plan-as-execute + verify. PARTIAL: terraform apply blocked by IAM.
- Consumer microservice content authored (app.py + Dockerfile + README.md).
- Docker image acdl-microservice:latest built.
- Adapter fixed: ref emission (bare), JSON-string jsonencode, ECS service
network_configuration/load_balancer/desired_count/launch_type/task_definition,
listener default_action/load_balancer_arn, target group target_type/vpc_id/protocol,
VPC tags (not name), IGW + route table association, managed_policy_arns list.
- L1 fixes: l1-ecs-service (removed port from service sub-resource),
l1-vpc (added intra_refs, removed igw_id output).
- Resolver: intra_refs resolution (refs between sub-resources of same L1).
- terraform validate + plan succeed (13 to add).
- terraform apply BLOCKED (AccessDenied — live IAM policy not updated).
- Evidence event TERRAFORM_APPLY_BLOCKED written to DynamoDB outbox.
- v1.1 S3 regression: byte-identical.
Ready to ship v1.2.5 (partial).
|
2026-07-21 22:21:36 +00:00 |
|
|
Jon Chery
|
4ed2542ecf
|
docs(P13): plan-as-execute + verify (v1.2.3)
---ci---
project: acdl
phase: 13
milestone: v1.2
status: verify
verdict: VERIFIED
requirements:
covered: [REQ-31]
---/ci---
Phase 13 plan-as-execute + verify. scripts/verify_phase13.sh green.
6 ECS L1s authored + registered (l1-vpc, l1-ecs-cluster, l1-ecs-service,
l1-iam-role, l1-alb, l1-ecr). Adapter generalized to table-driven
TYPE_MAP (12 IR types) + INPUT_MAP + OUTPUT_MAP. S3 regression: the v1.1
spike l1-s3 produces byte-identical main.tf. Ready to ship v1.2.3.
|
2026-07-21 21:05:48 +00:00 |
|
|
Jon Chery
|
e054a95fd5
|
phase: 9, status: plan-as-execute, persona: platform-engineer, task: T-9.1..T-9.4
---ci---
project: acdl
phase: 9
milestone: v1.1
status: plan-as-execute
persona: platform-engineer
task: [T-9.1, T-9.2, T-9.3, T-9.4]
requirements.covered: [REQ-24]
---/ci---
Wave 1: the IR-typed L1 module l1-s3.
- T-9.1: modules-ir/l1/l1-s3/interface.json - the L1 interface contract
(typed inputs bucket_name/region, outputs bucket_arn/bucket_name, NFR
versioning; type aws:s3:bucket). Per D-P09-2 this is a contract (typed
declarations), NOT an IR-schema instance.
- T-9.2: modules-ir/l1/l1-s3/spike_instance.json - a concrete stack
instance with values (bucket_name=acdl-spike-bucket, region=us-east-1)
that validates against schemas/ir.schema.json (verified).
- T-9.3: modules-ir/registry.json - the L1 registry, one entry
l1-s3@1.0.0 -> interface.json (D-P09-3, co-located with modules-ir/).
- T-9.4: modules-ir/l1/l1-s3/README.md - the L1 doc + the IR->Terraform
mapping table the adapter performs.
Spike instance validates against ir.schema.json; interface + registry
valid JSON.
|
2026-07-21 19:13:31 +00:00 |
|