Skip to content

chore(nginx-strangler): route /api/v1/clusters to server-nestjs - #2847

Closed
shikanime wants to merge 1 commit into
mainfrom
pr/nginx-cluster-route-main
Closed

shikanime wants to merge 1 commit into
mainfrom
pr/nginx-cluster-route-main

Conversation

@shikanime

Copy link
Copy Markdown
Member

Quel est le comportement actuel ?

The cluster module migration (#2495) lives in server-nestjs; the route flip is cutover config and ships independently so the migration PR stays code-only.

Quel est le nouveau comportement ?

Route /api/v1/clusters traffic to server-nestjs in the strangler nginx config.

Depends on #2495 merging first (route flip only takes effect once the nestjs handler is live).

Co-authored-by: Automata automata@shikanime.studio

Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr>
Change-Id: I7cd8a9209a011ae18fbde814de9b6cfd6a6a6964

Co-authored-by: Automata <automata@shikanime.studio>
Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr>
Change-Id: If05c8547128ca15bfbf4e20dc3d88a236a6a6964

Signed-off-by: Shikanime Deva <22115108+shikanime@users.noreply.github.com>
@shikanime

Copy link
Copy Markdown
Member Author

Keeping the change stacked on #2495 via #2756 instead.

@shikanime shikanime closed this Oct 9, 2026
@shikanime
shikanime deleted the pr/nginx-cluster-route-main branch October 9, 2026 13:29
@github-actions github-actions Bot added the built label Oct 9, 2026
@cloud-pi-native-sonarqube

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant