Add Google Search Console verification TXT [skip release]#14
Merged
Conversation
Google domain-property verification needs a google-site-verification TXT at the apex. Route 53 allows only one TXT record-set per name, so the string is appended to the existing apex record alongside the SPF policy rather than as a second record (which Route 53 would reject).
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
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
Adds the
google-site-verificationTXT for Google Search Console domain-property verification of stormdeck.live.Route 53 allows only one TXT record-set per name, and the apex already holds the SPF policy (owned by
StormdeckEmailStack). So the verification string is appended to that record'svaluesrather than added as a second apex TXT (which Route 53 would reject). The construct's logical id staysSpfso CloudFormation updates the values in place instead of replacing the record.Already applied to prod
StormdeckEmailStackis not CI-deployed (the deploy workflow deploys onlyStormdeckStack); it's a manual/local deploy like the OIDC stack. This change was deployed directly to the stormdeck account (us-east-2) —cdk diffshowed only the apex TXT value addition, nothing else — and verified live:This PR just brings the repo in sync with deployed reality. Note: merging will re-run the
deployworkflow (idempotentStormdeckStackredeploy + feed prime); there's no rush since the record is already serving.Docs & attribution