feat: deploy dev AWS infrastructure (Terraform) - live & verified - #14
Merged
Conversation
…e wiring - Point environments/dev/backend.tf at existing state bucket taskly-terraform-state-583168584925 - Create DynamoDB lock table taskly-terraform-locks (done via AWS CLI, ACTIVE) - Declare required secrets, DNS/email, and sizing variables in dev variables.tf plus previously-undeclared tfvars to avoid undeclared-variable warnings - Pass required root-module variables through environments/dev/main.tf - Gate DR route53 records (api_primary/api_secondary) on hosted_zone_id != "" so no DNS records are planned when the account has no hosted zone - Add infrastructure/.gitignore to exclude secret-bearing tfvars and state Verified: terraform init + validate succeed; plan (dummy secrets) = 211 to add, 0 errors, 0 aws_route53_record resources.
…f, fix S3 replication & monitoring ordering (FEAT-003)
PR Validation FailedOne or more checks failed. Please review the workflow logs for details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Deploys the full Taskly AWS infrastructure to the dev environment via Terraform, on top of the app fixes already merged in #13. The stack is live and verified healthy in account
583168584925/us-east-1.Result: live and healthy
terraform plan -detailed-exitcode→ 0 / "No changes" (fully converged, idempotent).GET https://bvju0gyni7.execute-api.us-east-1.amazonaws.com/api/health→ HTTP 200{"status":"OK",...,"database":"connected"}— proves the full API Gateway → Lambda (VPC) → DocumentDB path works.taskly-dev-api+ 3 processors: Active. DocumentDBtaskly-dev-docdb-cluster: available.Key outputs
https://bvju0gyni7.execute-api.us-east-1.amazonaws.comus-east-1_l0jRjqILWa1i9m0h2tqf5hu2ddpsq6bcdftaskly-dev-uploads-583168584925taskly-dev-apiBlockers resolved
environments/dev/backend.tfto the existing buckettaskly-terraform-state-583168584925; created the missing DynamoDB lock tabletaskly-terraform-locks.environments/dev/outputs.tf. Secrets kept in a gitignoredsecret.auto.tfvars(not committed).scripts/build-lambda.sh(full-backend bundle for all four handlers, pruned to fit the 250 MB limit); staged zips via targetedmodule.s3apply before full apply.hosted_zone_id.Manual prerequisites (account limitations — not fabricated)
AccessDenied: account must be verified). Open an AWS Support case, then setenable_cloudfront = trueand re-apply.taskly.appstays pending (account does not own the domain) — needs DNS records.hosted_zone_id+domain_nameonce a hosted zone exists.Cost & teardown
Estimated ~$130/mo (DocumentDB ~$60, NAT ~$32, VPC endpoints ~$28). Teardown:
terraform destroyfrominfrastructure/environments/dev.Review
Semantic review verdict: APPROVED (4 non-blocking notes documented). Plan + deployment report + review under
.tasks/task-deploy-infra/.No real secrets committed (verified: no
secret.auto.tfvars, state files, or credentials tracked).