Hide model registry features with package registry disabled
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
The model registry feature requires package registry to be enabled to function, since it implements models as a type of package. When package registry is disabled, for example at instance level, model registry can still be attempted to be used but is broken and unusable; for example, trying to upload a model from the UI attempts an API call PUT /api/v4/projects/:id/packages/ml_models/:model_id/files/:filename which fails with a 404. This causes a substandard and confusing user experience, as users aren't sure if they're doing something wrong (example support ticket, internal).
To improve this, I would suggest adding a visual UI indicator that the feature will be unusable without package registry being enabled, as well as greying it out so that the user can't attempt to do it anyway. The fact that package registry is a dependency should also be added to the documentation.
Tagging @fdegier as per request.
Steps
-
Add a visual UI indicator that the feature will be unusable without package registry being enabled, as well as greying it out so that the user can't attempt to do it anyway. -
The fact that package registry is a dependency should also be added to the documentation.