Dataiku DSSInstall

Overview

This node integrates with the Dataiku DSS API, enabling users to perform a wide range of operations on various Dataiku DSS resources. Specifically for the Plugin resource and the Fetch From Git Remote operation, it fetches the content of a plugin from a previously-declared git remote repository.

This functionality is useful when you want to synchronize your local plugin development environment with the latest changes from a remote Git repository without manually running Git commands outside of n8n. It helps automate plugin updates, ensuring that your Dataiku DSS plugins are up-to-date with the remote source.

Practical example:

• Automatically fetch the latest plugin code from a Git remote as part of a CI/CD workflow in n8n, so that any new commits pushed to the remote repository are reflected in your Dataiku DSS instance.

Properties

Output

The node outputs the response from the Dataiku DSS API call:

• For the Fetch From Git Remote operation on the Plugin resource, the output will be JSON data representing the result of the fetch action. This typically includes status information about the fetch operation.
• If the operation returns binary data (not typical for this operation), it would be provided as binary output, but this operation primarily returns JSON.
• In case of errors, the node throws an error with details about the failure.

Output format example (JSON):

{
  "status": "success",
  "message": "Fetched from git remote successfully"
}

(Note: Actual response fields depend on the Dataiku DSS API.)

Dependencies

• Requires a valid connection to a Dataiku DSS instance.
• Requires an API key credential for authenticating with the Dataiku DSS API.
• The node uses HTTP requests to communicate with the Dataiku DSS REST API.
• No additional external dependencies beyond the standard n8n environment and the configured Dataiku DSS API credentials.

Troubleshooting

• Missing Credentials Error: If the node throws "Missing Dataiku DSS API Credentials," ensure that you have configured the required API key credential in n8n.
• Required Parameter Errors: The node validates required parameters such as Plugin ID for this operation. Missing these will cause errors like "Plugin ID is required."
• API Request Failures: Network issues, incorrect server URL, or invalid API keys can cause request failures. Check the Dataiku DSS server URL and API key validity.
• Unexpected Response Format: If the API response cannot be parsed as JSON, the node attempts to return raw text or binary data. Ensure the API endpoint behaves as expected.
• Permission Issues: The API user must have sufficient permissions to fetch plugin data from the Git remote.

Links and References

• Dataiku DSS API Documentation
• Dataiku DSS Plugins Guide
• n8n Documentation - Creating Custom Nodes

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