Every route represents relation of path to permissions. You can add multiple routes to each access token.
The path must follow the given pattern: /{repository}/{gav}
:
{repository}
- required name of repository used to distinguish repositories{gav}
- optional GAV (group-artifact-version
) pathSome examples of path declaration and matched URLs:
Path | Matches | Status |
---|---|---|
/ | /releases/* /snapshots/* | Ok Ok |
/releases | /releases/* /snapshots/* | Ok Unauthorized |
/releases/groupId/artifactId | /releases/groupId/artifactId/* /releases/groupId/* /snapshots/* | Ok Unauthorized Unauthorized |
Currently supported permissions:
r
- allows token to read resources under the associated pathw
- allows token to write (deploy) resources under the associated pathYou can add access to specified route for token using the route-add <token> <path> <permissions>
command in Reposilite CLI.
$ route-add reposilite-publisher /releases/com/reposilite w
Route Route(path=/releases/com/reposilite, permissions=[WRITE]) has been added to token reposilite-publisher
You can remove access to specified route for token using the route-remove <token> <path>
command in Reposilite CLI.
$ route-remove reposilite-publisher /releases/com/reposilite
Token reposilite-publisher has been updated, new routes: []
Did you found a misleading and deprecated content, or maybe you just feel this section misses important elements?
Copyright © 2022 dzikoysk with ❤ panda-lang