GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves feature flags for a specific project in GitLab using the GitLab API. It is useful for scenarios where you need to manage or monitor feature flags within a project, such as enabling or disabling features dynamically based on project settings. For example, a developer or DevOps engineer might use this node to fetch all enabled or disabled feature flags for a project to automate deployment or testing workflows.

Use Case Examples

  1. Fetch all feature flags for a project by providing the project ID.
  2. Filter feature flags by their scope (enabled or disabled) to get a subset of flags.
  3. Paginate through feature flags using page and per_page parameters to handle large sets of flags.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request (boolean). Defaults to false.
Authentication The authentication method used for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent. Defaults to https://gitlab.com.
Method The HTTP method used for the API request. Defaults to GET.
Query Parameters Optional query parameters to filter and paginate the feature flags.
Path Parameters Path parameters required for the API endpoint.

Output

JSON

  • featureFlags - Array of feature flags retrieved from the project
  • pagination
    • page - Current page number of the results
    • per_page - Number of items per page in the results
    • total - Total number of feature flags available

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the authenticated user.
  • Check that the GitLab API key credential is valid and has sufficient permissions to access project feature flags.
  • If pagination parameters are used, verify that page and per_page values are within acceptable ranges to avoid empty or incomplete results.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (invalid project ID), and 400 Bad Request (invalid query parameters). Resolving these involves correcting credentials, project ID, or query parameters respectively.

Links

Discussion