Repository navigation
refactor(nginx-strangler): route stages to server-nestjs - #2748
Conversation
45a917f to
0258166
Compare
0258166 to
9688320
Compare
9688320 to
02fca72
Compare
|
🤖 Hey ! A preview of the application is available at : https://console-pr-2748.dso.cpin-hp.numerique-interieur.fr Please be patient, deployment may take a few minutes. |
dc75f9b to
c7ecbdf
Compare
|
PR réduite à la bascule nginx. Le câblage de Diff actuel : |
accf4b3 to
474f8a2
Compare
474f8a2 to
bec7d63
Compare
fd03fd1 to
1338e3e
Compare
StephaneTrebel
left a comment
There was a problem hiding this comment.
Approbation : la route stages cible la migration qui valide désormais les identifiants UUID. Fils résolus et CI verte.
1338e3e to
8bf3263
Compare
8bf3263 to
794a113
Compare
Co-authored-by: Automata <automata@shikanime.studio>
794a113 to
4e7d734
Compare
|
StephaneTrebel
left a comment
There was a problem hiding this comment.
La route est plus spécifique que le fallback , reste placée avant celui-ci et cible correctement server-nestjs. Les fils sont résolus et la CI est verte.
Revue remplacée : le shell a supprimé les chemins entre accents graves du verdict.
StephaneTrebel
left a comment
There was a problem hiding this comment.
La route /api/v1/stages est plus spécifique que le fallback /api/, reste placée avant celui-ci et cible correctement server-nestjs. Les fils sont résolus et la CI est verte.

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (55.60% Estimated after merge)
Issues liées
Depends on the server-nestjs stage routes from #2496; safe to merge only with or after it.
Quel est le comportement actuel ?
Decouple the traffic-routing cut-over from the stage module migration so the nginx switch can land and be observed independently of #2496.
Quel est le nouveau comportement ?
Extract the nginx-strangler routing change (
/api/v1/stages→ server-nestjs) from #2496 into this standalone PR.Signed-off-by: Shikanime Deva 22115108+shikanime@users.noreply.github.com