Allow access to project-level package files API with CI job token
What does this MR do and why?
Describe in detail what your merge request does and why.
Allow access to project-level package files API with CI job token
Currently job tokens have the ability to both manage package versions, as of !91437 (merged) and download individual package files across all package registry implementations, however the individual files in each release aren't currently managable.
Following the lead of the aformentioned changes, this MR allows management of package files on the project-level APIs.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
image: curlimages/curl:latest
test:
script:
- touch file.txt
- curl -H "JOB-TOKEN: $CI_JOB_TOKEN" --upload-file file.txt "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/generic/my_package/0.0.1/file.txt"
- curl -H "JOB-TOKEN: $CI_JOB_TOKEN" "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/1/package_files"
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.