GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows creating a new error tracking client key for a specific project in GitLab. It is useful for developers and DevOps teams who want to manage error tracking keys programmatically within their CI/CD pipelines or automation workflows. For example, it can be used to automate the setup of error tracking for new projects or to rotate client keys securely.

Use Case Examples

  1. Automate creation of error tracking client keys for new GitLab projects.
  2. Integrate error tracking key management into deployment pipelines.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
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 POST is used for this operation.
Path Parameters Parameters to be included in the request path, specifically the project ID or URL-encoded path.

Output

JSON

  • id - The unique identifier of the created error tracking client key.
  • name - The name of the error tracking client key.
  • public_key - The public key associated with the error tracking client key.
  • created_at - Timestamp when the client key was created.
  • updated_at - Timestamp when the client key was last updated.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the project ID provided in path parameters is correct and accessible by the authenticated user.
  • Verify that the authentication token has sufficient permissions to create error tracking client keys.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid project ID), and 403 Forbidden (insufficient permissions).

Links

Discussion