Skip to content

Expose package_registry_access_level in project API endpoints

Nejc Habjanrequested to merge
gitlab-community/gitlab-org/gitlab:feat/package-access-level into master
  • Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.

What does this MR do and why?

Exposes package_registry_access_level in project API endpoints and deprecates packages_enabled in the API - similar to container_registry_enabled deprecated in favor of container_registry_access_level.

Closes #454759 (closed)

🛠 with ❤ at Siemens as part of the GitLab DACH Connect Roadshow & Hackathon

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

TODO

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. set up local GDK or GitPod
  2. Go to e.g. `http://localhost:3000/api/v4/projects/gitlab-org%2Fgitlab-shell
  3. check presence of package_registry_access_level attribute in JSON response
Edited by 🤖 GitLab Bot 🤖

Merge request reports