Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API

Actions364

Overview

This node integrates with the Dataiku DSS API, enabling users to perform a wide range of operations on Dataiku DSS resources directly from n8n workflows. Specifically for the Plugin resource and the Set Git Remote Info operation, it allows setting or updating the information about the git remote repository associated with a plugin.

Common scenarios where this node is beneficial include automating plugin management tasks such as configuring git remotes for plugins, managing plugin files, synchronizing plugin code with git repositories, and more. For example, a user can automate the process of linking a plugin to a specific git remote URL, facilitating version control and collaboration workflows.

Properties

Name Meaning
Plugin ID The unique identifier of the plugin for which the git remote information will be set.
Request Body A JSON object containing the details to set for the git remote info (e.g., remote URL, branch, credentials).

Output

The node outputs the response from the Dataiku DSS API call in the json field of the output data. This typically contains confirmation or details of the updated git remote information for the specified plugin.

If the operation involves downloading files or binary content (not applicable specifically for "Set Git Remote Info"), the node would output binary data accordingly. However, for this operation, the output is JSON data representing the result of the API request.

Dependencies

  • Requires an active connection to a Dataiku DSS instance.
  • Requires valid API credentials (an API key) for authenticating with the Dataiku DSS API.
  • The node expects the Dataiku DSS server URL and user API key to be configured in the credentials.

Troubleshooting

  • Missing Credentials Error: If the node throws an error about missing Dataiku DSS API credentials, ensure that the API key credential is properly configured in n8n.
  • Required Parameter Errors: The node validates required parameters such as Plugin ID before making the API call. If you see errors indicating missing parameters, verify that all required fields are correctly set.
  • API Request Failures: Network issues, incorrect server URLs, or invalid API keys can cause request failures. Check connectivity and credential validity.
  • Invalid JSON in Request Body: Ensure that the JSON provided in the Request Body property is well-formed and matches the expected schema for setting git remote info.

Links and References


This summary focuses on the Plugin resource and the Set Git Remote Info operation as requested, based on static analysis of the provided source code and input properties.

Discussion