A removed domain is released while its route still serves traffic
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- docker, typescript
Rechercherichtung
Start with apps/api/src/modules/apps/infrastructure/prisma-application.store.ts and the syncDomains behavior described in the issue. Then trace how the deployment pipeline tracks active releases and route changes, since the fix must coordinate reservation release with route removal. Add a test for removing a domain without redeploying and attempting to claim it from another application; done means the claim is rejected while the route still exists or is switching.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
What
Removing a domain from an application's configuration deletes its reservation at once (syncDomains in apps/api/src/modules/apps/infrastructure/prisma-application.store.ts). The release that is still running keeps serving that domain through Caddy until the next successful deployment, and for longer if that deployment fails.
Meanwhile another application of the same organization can claim the domain. The reservation and the live route then name two different applications, and traffic can reach the wrong service.
Found by a security audit of the repository on 8 November 2026, still true on main. The audit reproduced the reassignment at the store level; the full behavior with Caddy has not been tested.
Design question
A reservation should last as long as something can serve the domain. Options:
- Keep the reservation while the active release, or a deployment in progress, still lists the domain; release it when the route is removed.
- Mark it as "releasing" and refuse new claims until the route is gone.
Both need the deployment pipeline to tell the apps module when a route was removed.
Done when
- A domain cannot be claimed by another application while a route for it exists or is being switched.
- A test covers: remove the domain, do not redeploy, try to claim it from another application.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2
- Forks
- 1
- Ø Merge
- 7 Std. 17 Min.
- Gemergte PRs (30 T.)
- 197
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus shipkeepdev/shipkeep
-
good first issue
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
shipkeepdev/shipkeep#295 ·
Maintainer antworten meist innerhalb von 1 Tag
-
good first issue priority:P2 track:control-plane
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
shipkeepdev/shipkeep#212 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue priority:P3 track:web
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
shipkeepdev/shipkeep#144 ·
Maintainer antworten meist innerhalb von 1 Tag
-
documentation good first issue priority:P3 track:control-plane
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
shipkeepdev/shipkeep#143 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue priority:P3 track:control-plane
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
shipkeepdev/shipkeep#142 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in shipkeepdev/shipkeep
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
vercel-labs/ui#540 ·
Maintainer antworten meist innerhalb von 1 Tag
-
accepted ai-dev ai-implementing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
livesport/homer#218 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
figma/code-connect#419 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
Negative values skip k/M abbreviation and medium decimal format on line, stacked-area, and tooltipOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
britecharts/britecharts#1255 ·
Maintainer antworten meist innerhalb von 1 Tag