Repository navigation
Conversation
…: MX + SES DKIM) Co-authored-by: Cursor <cursoragent@cursor.com>
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|
PR Description Check PassedAll required sections are filled in correctly. Details |
This branch has not been deployed
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.
Description
New template
withwillow.ai/agent-emailfor Willow (same provider aswithwillow.ai/run-host, #2844). It lets a domain owner connect a domain (for exampleagents.example.com) so Willow background agents receive and send email at it: one MX record routes the domain's mail to Amazon SES, which Willow receives it through, and three CNAMEs publish the domain's Amazon SES Easy DKIM keys.The MX target and the DKIM targets are fixed; only the three DKIM tokens SES generated for the domain are variables. The template is meant for a dedicated subdomain (passed with the
hostparameter); Willow already refuses domains whose MX points elsewhere.No
redirect_uriis used (Willow polls the records after the user approves), sosyncRedirectDomainis not set.Type of change
How Has This Been Tested?
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserverdc-template-linter -merge-or-failanddc-template-linter -cloudflare -logospass.Checklist of common problems
syncPubKeyDomainis setwarnPhishingis not set alongsidesyncPubKeyDomainsyncRedirectDomainis set whenever the template usesredirect_uriin the synchronous flow (not used)txtConflictMatchingModeis set on every TXT record that must be unique (no TXT records)%dkimN%.dkim.amazonses.com)hostlabel (%dkimN%._domainkey)hostfield to create a subdomain (thehostparameter is used)%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon records the end user may need to modify or remove (none: all four are needed for mail to work)Online Editor test results
Editor test link(s):