Skip to content

Feature proposal: Add a User Interface for publishing packages

Release notes

Added a User Interface for publishing packages.

Problem to solve

As a user publishing a Composer package in the GitLab package registry, I do not want to use the command line to send a request to the GitLab API via curl --data tag=<tag> "https://__token__:<personal-access-token>@gitlab.example.com/api/v4/projects/<project_id>/packages/composer"

Intended users

User experience goal

On the package registry page, "publish package" button. Upon clicking the button a form would be displayed allowing me to select the tag or git branch to publish. I would click "Publish" to complete.

Proposal

Simply add a button and form in the UI that accomplishes the same thing as the curl --data tag=<tag> "https://__token__:<personal-access-token>@gitlab.example.com/api/v4/projects/<project_id>/packages/composer" call.

Further details

Permissions and Security

  • Add expected impact to members with no access (0)
  • Add expected impact to Guest (10) members
  • Add expected impact to Reporter (20) members
  • Add expected impact to Developer (30) members
  • Add expected impact to Maintainer (40) members
  • Add expected impact to Owner (50) members -->

Documentation

Add a "Publish a Composer package by using the UI" section to https://gitlab.acquia.io/help/user/packages/composer_repository/index.md#publish-a-composer-package-by-using-cicd

Availability & Testing

Available Tier

  • Free
  • Premium/Silver
  • Ultimate/Gold

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Matthew Grasmick