feat: add weave and slack records to patchworklabs.org - #3
Open
jaspermayone wants to merge 1 commit into
Open
jaspermayone wants to merge 1 commit into
jaspermayone wants to merge 1 commit into
Conversation
jaspermayone
requested review from
youngchief-btw
and removed request for
a team
September 28, 2026 21:26
octoDNS planpatchworklabs.org.cloudflare
Meta: {'cloudflare_plan': {'current': None, 'desired': 'free'}} Summary: Creates=18, Updates=0, Deletes=0, Existing=0, Meta=True hackathon.help.cloudflare
Summary: Creates=1, Updates=0, Deletes=0, Existing=4, Meta=False Planned against |
jaspermayone
added this pull request to stack #4
September 28, 2026 21:34
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.
What does this change?
This change puts the Weave records that are live in Cloudflare into
patchworklabs.org.yaml. It also adds the newslack.patchworklabs.orgrecord.slack129.213.163.213weave129.213.163.213send.weave10 feedback-smtp.us-east-1.amazonses.com.send.weavev=spf1 include:amazonses.com ~allresend._domainkey.weaveslackby hand in Cloudflare on 2026-09-28. Weave redirects it tohttps://weave.patchworklabs.org/slack(feat(slack): require full slack membership and expose it via oidc weave#121). Traefik on alastor routes it (jaspermayone/infra#20).weaverecords were already live but missing from git. Without them, the first working deploy would delete them, and Weave would lose its host and its email.This PR is stacked on #2. It uses the owner comments and TTLs from #2.
Who owns the records?
@patchworklabsorg/infra, the same as the other records in #2.Checklist
GitHub handle.
./bin/validatepasses, so the records are in the order octoDNS wants.octoDNS plancomment on this pull request and itchanges only what I expected. The plan cannot run until the token covers
patchworklabs.org(see feat: check zone files for owners, ttl and cloudflare rules #2).Anything else a reviewer should know?
Some other live records are also not in git. This PR does not add them, because I do not know their owners:
weave-kyc-proposal(CNAME to Vercel)cio160924.cio(MX and TXT for Mailgun)cio._domainkey.cio160924.cio(TXT)_dmarc.cio(TXT)A deploy would delete them. The
MAX_DELETESguard stops that deploy, but somebody must add these records or remove them on purpose.