Repository navigation
Conversation
L'API est servie intégralement par server-nestjs : les endpoints V1 /api/v1/environments et /api/v1/repositories ne sont pas repris (équivalents V2 sous /api/v2/projects/:projectId/), le Swagger historique /swagger-ui renvoie 404 au profit de /swagger-ui-server-nestjs, l'authentification navigateur passe par un jeton Bearer Keycloak résolu côté backend, et une date d'expiration vide à la création d'un jeton d'API équivaut à l'absence d'expiration. Co-authored-by: Automata <automata@shikanime.studio>
Open
4 tasks
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.
Quoi
Mise à jour de la page IAM (
docs/platform/iam.md) pour refléter l'état actuel de la Console :fastify-keycloak-adapteret un stockage en session, ce qui ne décrit plus le flux servi par server-nestjs ;/api/v1/environmentset/api/v1/repositories(équivalents V2 sous/api/v2/projects/:projectId/) ;/swagger-ui(404), remplacé par/swagger-ui-server-nestjs;Pourquoi
La Console sert désormais toute son API via le backend NestJS : le trafic applicatif legacy est fermé (console#2927) et les routes admin tokens et system settings ont été basculées vers server-nestjs (commits console 5618a220, ab27124a, 85eecbb4). Par ailleurs, le schéma de création de jeton accepte de nouveau une date d'expiration vide (commit eea6fd6a). La page décrivait encore l'ancien flux de cohabitation des deux backends.
Références