GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation renews the secret of a specific application in GitLab by making a POST request to the GitLab API endpoint `/api/v4/applications/{id}/renew-secret`. It is useful for scenarios where an application secret needs to be refreshed for security reasons or to maintain access credentials.

Use Case Examples

  1. Renew the secret of an application with a given ID to ensure secure API access.
  2. Automate the process of rotating application secrets in GitLab to comply with security policies.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for testing or public endpoints.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is POST for this operation.
Path Parameters Parameters to be included in the request path, specifically the application ID to identify which application's secret to renew.

Output

JSON

  • id - The ID of the application whose secret was renewed.
  • secret - The new secret generated for the application.
  • name - The name of the application.
  • redirect_uri - The redirect URI associated with the application.
  • created_at - Timestamp when the application was created.
  • updated_at - Timestamp when the application was last updated.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the application ID provided in the path parameters is correct and exists in GitLab.
  • Verify that the GitLab API key credential has sufficient permissions to renew application secrets.
  • If authentication is skipped, the request may fail due to lack of authorization.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.

Links

Discussion