GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation performs a search for Conan packages within a specific GitLab project using the GitLab API. It is useful for developers or DevOps engineers who want to query Conan packages stored in a GitLab project's package registry, filtering results based on a search query. For example, it can be used to find specific Conan packages by name or pattern within a project.

Use Case Examples

  1. Searching for Conan packages in a project by specifying the project ID and a search query string.
  2. Automating package discovery in CI/CD pipelines by querying the GitLab package registry for Conan packages matching certain criteria.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically a GitLab API key.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, default is GET.
Query Parameters Query parameters for the API request, including the search query 'q' to filter Conan packages.
Path Parameters Path parameters for the API request, including the project 'id' to specify which project to search in.

Output

JSON

  • id - The unique identifier of the Conan package.
  • name - The name of the Conan package.
  • version - The version of the Conan package.
  • description - Description of the Conan package.
  • created_at - Timestamp when the package was created.
  • updated_at - Timestamp when the package was last updated.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the provided authentication.
  • Verify that the search query parameter 'q' is properly formatted and not empty, as it is required.
  • Check that the GitLab API key credential is valid and has sufficient permissions to access the project's package registry.
  • Common error messages may include authentication failures, 404 not found if the project ID is invalid, or 400 bad request if required parameters are missing or malformed.

Links

Discussion