Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin-add doesn't work for Gitlab registries #252

Open
Xilonz opened this issue Oct 25, 2024 · 0 comments
Open

Plugin-add doesn't work for Gitlab registries #252

Xilonz opened this issue Oct 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Xilonz
Copy link

Xilonz commented Oct 25, 2024

The plugin-add command doesn't work for Gitlab registries.
The required metadata { lando: {} } or { keywords: ['lando-plugin']] are not exposed through the api.

Example Gitlab NPM metadata for the package:

{"name":"@arjan/lando-hostfile","versions":{"0.0.1":{"dist":{"shasum":"ebcfcd755ecbba3958541f477b80dbf6db1b348d","tarball":"https://my-personal-gitlab.nl/api/v4/projects/355/packages/npm/@arjan/lando-hostfile/-/@arjan/lando-hostfile-0.0.1.tgz"},"name":"@arjan/lando-hostfile","version":"0.0.1","dependencies":{"lodash":"^4.17.20"}}},"dist-tags":{"latest":"0.0.1"}}

Proposed solution:
Add an argument to --force the installation, skipping the validation.
Since Gitlab is planning to add full meta support, I don't think any additional changes are needed.

GitLab's tracking issue for full metadata support:
https://gitlab.com/gitlab-org/gitlab/-/issues/344107

@Xilonz Xilonz added the bug Something isn't working label Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant