A removed domain is released while its route still serves traffic
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- docker, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2
- Forks
- 1
- Merge medio
- 7 h 17 min
- PR fusionados (30 d)
- 197
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de shipkeepdev/shipkeep
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
shipkeepdev/shipkeep#295 ·
Los mantenedores suelen responder en 1 día
-
good first issue priority:P2 track:control-plane
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
shipkeepdev/shipkeep#212 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue priority:P3 track:web
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
shipkeepdev/shipkeep#144 ·
Los mantenedores suelen responder en 1 día
-
documentation good first issue priority:P3 track:control-plane
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
shipkeepdev/shipkeep#143 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue priority:P3 track:control-plane
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
shipkeepdev/shipkeep#142 ·
Los mantenedores suelen responder en 1 día
Todos los issues de shipkeepdev/shipkeep
Issues similares
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
figma/code-connect#419 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Los mantenedores suelen responder en 2 días
-
A live recovery copy treats a large whole number and text with the same digits as the same valueAbiertobug sharing & sync
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día