fix(infra): address PR review feedback on tf modules
Deployer role: - Add servicediscovery actions; module always creates Cloud Map namespace and service so the policy must grant CreatePrivateDnsNamespace etc. - Make Route53 + ACM permissions unconditional. The server module always issues an ACM cert and writes Route53 records (no CloudFront default-cert path exists), so gating these on route53_zone_ids was broken. Split Route53 into hosted-zone management (always) plus record-set mutation (scoped to caller-supplied zones, falls back to *). - Remove unused cloudfront:* statement; no CloudFront resources in module. - Replace acm:* wildcard with explicit cert-management action set. Server module: - qdrant_image_tag is now nullable with default null and validated against use_external_qdrant, so external-qdrant callers can omit it instead of passing a sentinel "unused" value. - task_role_arn and efs_id outputs marked sensitive; qdrant_dns_name returns null when use_external_qdrant = true. - ALB SG now has matching IPv6 egress rule (was v4-only). - nextcloud_url validates the https:// scheme. - random_pet.subdomain keeper includes zone_name so a zone migration that preserves zone_id still triggers regeneration. - Pin required_version >= 1.9 on both modules. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.7
parent
ccf4b91bf9
commit
e4c552cd19
@@ -3,8 +3,11 @@ resource "random_pet" "subdomain" {
|
||||
separator = "-"
|
||||
|
||||
# Stable across applies; regenerate only if we point at a different zone.
|
||||
# `zone_name` is in the keeper too so a zone migration that keeps the same
|
||||
# zone_id (rare but possible across providers) still triggers regeneration.
|
||||
keepers = {
|
||||
zone_id = var.zone_id
|
||||
zone_id = var.zone_id
|
||||
zone_name = var.zone_name
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user