Dataiku DSS icon

Dataiku DSS

Use the Dataiku DSS API

Actions364

Overview

The node integrates with the Dataiku DSS API, enabling users to perform a wide range of operations on Dataiku DSS resources. Specifically for the Project Deployer resource and the Get Project Settings operation, it retrieves the settings of a published project from the Dataiku Project Deployer service.

This node is beneficial in scenarios where automation or integration workflows need to programmatically access deployment configurations of Dataiku projects. For example, you might want to fetch project deployment settings to audit configurations, trigger conditional logic based on deployment parameters, or synchronize settings across environments.

Properties

Name Meaning
Project Key The unique identifier key of the Dataiku project whose deployer settings you want to get.

Note: The property is a string input representing the project key and is required for this operation.

Output

The output of the node is a JSON object containing the settings of the specified published project in the Project Deployer. The exact structure depends on the Dataiku DSS API response but typically includes configuration details such as deployment parameters, environment settings, and other metadata related to the deployed project.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • Missing Credentials Error: If the API credentials are not provided or invalid, the node will throw an error indicating missing credentials. Ensure that the API key credential is correctly set up in n8n.
  • Missing Project Key: The operation requires the "Project Key" property. If omitted, the node throws an error stating that the project key is required.
  • API Request Failures: Network issues, incorrect server URLs, or insufficient permissions can cause API request failures. Check connectivity, verify the server URL, and ensure the API key has sufficient privileges.
  • Unexpected Response Format: If the API returns unexpected data or errors, the node may fail to parse the response. Review the API response and confirm the requested project exists and is accessible.

Links and References


This summary focuses on the "Project Deployer" resource and the "Get Project Settings" operation as requested, based on static analysis of the provided source code and properties.

Discussion