feat(server-nestjs): expose repository API v2 routes - #2408
Open
KepoParis wants to merge 1 commit into
Open
Conversation
KepoParis
force-pushed
the
feat/repository-api-v2
branch
from
August 4, 2026 13:24
705a742 to
8204c0e
Compare
KepoParis
changed the title
KepoParis
marked this pull request as ready for review
August 4, 2026 13:30
KepoParis
force-pushed
the
feat/repository-api-v2
branch
from
August 4, 2026 14:14
8204c0e to
2946302
Compare
KepoParis
force-pushed
the
feat/repository-v2-service
branch
from
August 4, 2026 14:14
ad92b92 to
904646f
Compare
KepoParis
force-pushed
the
feat/repository-api-v2
branch
from
August 5, 2026 13:50
2946302 to
4288f08
Compare
KepoParis
force-pushed
the
feat/repository-v2-service
branch
2 times, most recently
from
August 5, 2026 15:07
0c36bfd to
5352db8
Compare
KepoParis
force-pushed
the
feat/repository-api-v2
branch
from
August 5, 2026 15:07
4288f08 to
0ab0a44
Compare
KepoParis
force-pushed
the
feat/repository-v2-service
branch
from
August 5, 2026 15:39
5352db8 to
fc2762c
Compare
KepoParis
force-pushed
the
feat/repository-api-v2
branch
from
August 5, 2026 15:39
0ab0a44 to
ce2a119
Compare
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
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
2 participants
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.
Issues liées
Issues numéro:
Quel est le comportement actuel ?
La gestion des repositories est uniquement exposée par l'API v1 (legacy).
Quel est le nouveau comportement ?
Exposition de l'API v2 des repositories dans
server-nestjs, montée sous/api/v2/projects/:projectId/repositories:GET /200ListProjects(admin) +ListRepositories(projet)POST /201ManageRepositorieshumanPUT /:repositoryId200ManageRepositoriesDELETE /:repositoryId204ManageRepositoriesDétails :
ProjectGuardsur le controller : leprojectIddu chemin est résolu en contexteprojet, injecté par
@Project(), l'utilisateur par@AuthUser().@RequireProjectStatus('initializing', 'created', 'failed', 'warning'),@RequireProjectLocked(false)et@RequireUserType('human')(équivalent du!perms.userlegacy). LeGETn'en porteaucune.
ZodValidationPipeavecCreateRepositorySchema/UpdateRepositorySchema, etrepositoryIdvalidé parParseUUIDPipe.RepositoryModuledansmain.module.ts.Cette PR introduit-elle un breaking change ?
Non. L'API v1 reste inchangée ; la v2 est ajoutée en parallèle.
Autres informations
Reste à faire dans une PR de suivi, hors de cette pile :
sync), qui reste servie par le serveur legacyexternalTokenvers Vaultupdate