GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation retrieves the job token scope allowlist for a specific project in GitLab using the GitLab API. It is useful for users who want to programmatically access the list of allowed job token scopes for a project, which can help in managing CI/CD security and permissions. For example, a DevOps engineer might use this node to automate the auditing of job token scopes across multiple projects.

Use Case Examples

  1. Retrieve the job token scope allowlist for project ID 123 to verify which job token scopes are permitted.
  2. Automate monitoring of job token scope allowlists for compliance purposes.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Optional query parameters for pagination, including page number and items per page.
Path Parameters Path parameters required for the API request, specifically the project ID.

Output

JSON

  • response - The JSON response from the GitLab API containing the job token scope allowlist data

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the project ID path parameter is correctly set and corresponds to an existing project in GitLab.
  • Verify that the API authentication credentials are valid and have sufficient permissions to access the project's job token scope allowlist.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages may include authentication failures, 404 not found if the project ID is invalid, or permission denied errors. Resolving these typically involves correcting credentials, project ID, or user permissions.

Links

Discussion