GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation authorizes access to a specific file within a machine learning model version stored in a GitLab project. It is useful for managing permissions and access control for ML model files in GitLab's ML model registry. For example, it can be used to programmatically authorize a user or system to access a particular model file before downloading or using it in a pipeline.

Use Case Examples

  1. Authorize access to a file named 'model.pkl' in a specific ML model version within a GitLab project by providing the project ID, model version ID, and file name.
  2. Use this operation to manage file access permissions in automated ML workflows integrated with GitLab.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
Authentication The authentication method used for the request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but PUT is used for this operation.
Path Parameters Parameters required in the request path to identify the project, model version, and file name.

Output

JSON

  • authorization_status - Indicates whether the file authorization was successful or not.
  • message - Additional information or message returned from the authorization request.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID, model version ID, and file name are correctly specified and URL-encoded if necessary.
  • Verify that the API key credential has sufficient permissions to authorize file access in the GitLab project.
  • Check the base URL to ensure it points to the correct GitLab instance if using a self-hosted GitLab server.
  • Common error messages may include 401 Unauthorized (invalid or missing API key), 404 Not Found (incorrect project, model version, or file name), or 403 Forbidden (insufficient permissions).

Links

Discussion