feat(aws/route53): add DKIM and dystopia.city apex records - #714
Conversation
Extend the route53 module to cover Google Workspace mail authentication
across both hosted zones and Search Console verification for dystopia.city:
- TXT google._domainkey.panicboat.net : Google Workspace DKIM public key.
- TXT dystopia.city : google-site-verification token.
- MX dystopia.city : "1 smtp.google.com." (single-record
Google Workspace).
- TXT google._domainkey.dystopia.city : Google Workspace DKIM public key.
Rename the panicboat DKIM resource from google_domainkey_txt to
panicboat_net_google_domainkey_txt for symmetry now that a second zone
carries the same selector. State migration used a moved block that was
applied and then removed within this branch (subsequent plan clean).
Both DKIM keys exceed the 255-char DNS <character-string> limit, so the
values are split into two adjacent character-strings inside a single RR
(the AWS provider wraps the whole value in outer quotes, so only the
inner `" "` boundary is emitted here).
Signed-off-by: panicboat <panicboat@gmail.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Route53 module now documents both hosted zones and adds Google Workspace DKIM, verification TXT, and MX records for ChangesGoogle Workspace DNS configuration
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
google._domainkey.panicboat.net,google._domainkey.dystopia.city).dystopia.cityapex.1 smtp.google.com.) on thedystopia.cityapex.panicboat_net_google_domainkey_txtfor symmetry with the newly added dystopia counterpart. State migration used a temporarymovedblock that has already been consumed and removed within this branch.Notes
<character-string>limit, so each value is split into two adjacent character-strings inside a single RR (RFC 1035 concatenates them for the receiver). The AWS provider wraps the whole value in outer quotes on our behalf, so only the inner" "boundary is emitted in HCL.movedblock was applied and then removed within the same branch; a subsequentterragrunt planreports "No changes."Test plan
terragrunt planclean before each apply stage.terragrunt applysucceeded for each record — visible viaaws route53 list-resource-record-setsanddig @8.8.8.8.terragrunt planafter removing themovedblock reports "No changes."dystopia.city.dystopia.cityworks end-to-end.Summary by CodeRabbit
panicboat.netanddystopia.city.dystopia.city.