{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-dataiku-dataiku-dss","slug":"dataiku-dss","name":"Dataiku DSS","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=dataiku.dataiku-dss","page_url":"https://unfragile.ai/dataiku-dss","categories":["code-editors"],"tags":["AI","Artificial Intelligence","Data Science","Dataiku","DSS","keybindings","Machine Learning"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-dataiku-dataiku-dss__cap_0","uri":"capability://code.generation.editing.bidirectional.code.recipe.synchronization.with.remote.dss.instance","name":"bidirectional code recipe synchronization with remote dss instance","description":"Enables real-time editing of Python and R code recipes stored in a Dataiku DSS instance directly within VS Code's editor, with automatic persistence back to the remote DSS platform via authenticated API calls. The extension maintains a local working copy of recipe files while syncing changes bidirectionally through the DSS REST API using personal API key authentication, allowing developers to leverage VS Code's native editing experience without switching to the DSS web UI.","intents":["I want to edit my DSS recipes in VS Code instead of the web UI","I need to use VS Code's code completion and linting for my DSS Python/R recipes","I want to keep my recipes in sync between local edits and the remote DSS instance"],"best_for":["data engineers and data scientists already using Dataiku DSS who prefer VS Code as their primary editor","teams migrating from DSS web UI workflows to IDE-based development","developers building complex recipes who need advanced editor features like multi-file refactoring"],"limitations":["Requires DSS instance version 6.0.0 or higher; feature availability varies by DSS version","Bidirectional sync is file-level only — no conflict resolution for simultaneous edits in VS Code and DSS web UI","Cannot edit non-code DSS artifacts (datasets, flows, visual recipes) — only code recipes, libraries, and plugins","Network latency on recipe save depends on DSS instance responsiveness; no offline editing capability"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with access to target DSS instance","VS Code (version not specified in documentation)","Network connectivity to configured DSS instance URL"],"input_types":["Python code (recipe files)","R code (recipe files)","Plain text (wiki articles)"],"output_types":["Python code (persisted to DSS)","R code (persisted to DSS)","Plain text (persisted to DSS)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_1","uri":"capability://automation.workflow.remote.recipe.execution.with.live.log.streaming","name":"remote recipe execution with live log streaming","description":"Allows developers to trigger execution of Python and R recipes on a connected Dataiku DSS instance directly from VS Code via a status bar button, with real-time streaming of execution logs back to the VS Code output window. The extension sends execution requests through the DSS REST API and polls for completion status while displaying stdout/stderr output, enabling rapid iteration without leaving the editor.","intents":["I want to test my recipe changes immediately without switching to the DSS web UI","I need to see execution logs and debug output from my recipes in real-time","I want to iterate quickly on recipe development with fast feedback loops"],"best_for":["data engineers debugging recipe logic during development","teams using test-driven development for data pipelines","developers who need tight feedback loops between code edits and execution"],"limitations":["Execution happens on the remote DSS instance, not locally — requires network connectivity and DSS availability","No built-in timeout or cancellation mechanism documented; long-running recipes may block the extension","Log streaming is unidirectional (server to client only) — cannot send input to running recipes","Execution context is limited to the DSS instance's environment; cannot access local files or environment variables"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with recipe execution permissions","Network connectivity to DSS instance","Recipe must be valid and executable on the DSS instance"],"input_types":["Recipe file path (implicit from current editor context)","Execution parameters (if supported by recipe)"],"output_types":["Execution logs (stdout/stderr)","Execution status (success/failure)","Execution metadata (duration, resource usage if available)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_10","uri":"capability://automation.workflow.output.window.log.streaming.for.recipe.execution.feedback","name":"output window log streaming for recipe execution feedback","description":"Streams execution logs from remote recipe runs directly into VS Code's output window, displaying stdout and stderr output in real-time as the recipe executes on the DSS instance. The extension polls the DSS API for log updates and appends them to the output window, providing immediate feedback without requiring navigation to the DSS web UI.","intents":["I want to see recipe execution logs in real-time without switching to the DSS web UI","I need to debug recipe failures by examining stdout and stderr output","I want to monitor long-running recipes and see progress updates"],"best_for":["data engineers debugging recipe logic and errors","developers monitoring recipe execution during development","teams using VS Code as the primary development environment for DSS"],"limitations":["Log streaming is unidirectional (server to client) — cannot send input to running recipes or interact with the execution","Polling-based log updates may have latency; real-time streaming is not guaranteed","Log output is limited to stdout/stderr — no access to DSS execution metrics or resource usage","Output window is shared with other VS Code extensions — logs may be mixed with other output"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with recipe execution permissions","Network connectivity to DSS instance","Recipe execution triggered via status bar button or command"],"input_types":["Recipe execution request (implicit from status bar button or command)"],"output_types":["Execution logs (stdout/stderr)","Execution status updates","Execution completion status"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_2","uri":"capability://automation.workflow.local.recipe.execution.with.dataiku.package.integration","name":"local recipe execution with dataiku package integration","description":"Enables execution of Python and R recipes locally within VS Code using the locally-installed dataiku package, allowing developers to test recipes against local data or development datasets without requiring a remote DSS instance. The extension delegates execution to VS Code's native Python or R extension (e.g., Microsoft Python Extension) while providing the dataiku package context for DSS-specific operations.","intents":["I want to test my recipe locally before pushing to the DSS instance","I need to debug recipes with local data or development datasets","I want to avoid network latency and DSS instance availability issues during development"],"best_for":["data engineers developing recipes offline or with unreliable network connectivity","teams using local development environments before deploying to production DSS instances","developers who need fast feedback loops without depending on shared DSS infrastructure"],"limitations":["Requires local installation of dataiku Python or R package — adds setup complexity and version management overhead","Local execution environment may differ from DSS instance environment (Python version, library versions, system dependencies), leading to environment parity issues","Cannot access DSS datasets or flows directly — only works with local data or files","Requires manual configuration of Python/R interpreter path in extension settings; no auto-detection documented"],"requires":["Python 3.x with dataiku package installed locally (for Python recipes)","R with dataiku package installed locally (for R recipes)","Microsoft Python Extension or equivalent R extension installed in VS Code","Correct Python/R interpreter path configured in extension settings"],"input_types":["Python code (recipe files)","R code (recipe files)","Local data files (CSV, JSON, Parquet, etc.)"],"output_types":["Execution logs (stdout/stderr)","Local output files (if recipe writes to disk)","Execution status (success/failure)"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_3","uri":"capability://tool.use.integration.project.and.plugin.structure.browsing.with.sidebar.navigation","name":"project and plugin structure browsing with sidebar navigation","description":"Provides a dedicated sidebar panel in VS Code that displays the hierarchical structure of Dataiku DSS projects and plugins, allowing developers to browse, expand, and navigate to specific artifacts (recipes, libraries, plugins, wiki articles) without leaving the editor. The extension queries the DSS REST API to populate the tree view and handles file opening/creation through standard VS Code file operations.","intents":["I want to see all my DSS projects and plugins in a familiar tree view","I need to quickly navigate to a specific recipe or library file without searching","I want to understand the structure of my DSS projects at a glance"],"best_for":["data engineers managing multiple DSS projects with complex artifact hierarchies","teams onboarding new developers who need to explore project structure","developers who prefer visual navigation over command-line or search-based discovery"],"limitations":["Tree view is read-only for browsing; file creation/deletion requires additional steps through context menus or commands","No search or filtering within the tree view — must manually expand folders to find artifacts","Tree refresh is manual or event-driven; no real-time updates if artifacts are created/deleted in DSS web UI while VS Code is open","Sidebar space is limited; large projects with many artifacts may result in deep nesting and poor UX"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with read access to projects and plugins","Network connectivity to DSS instance"],"input_types":["DSS instance URL and API key (configuration)"],"output_types":["Hierarchical tree view of projects, plugins, and artifacts","File paths for selected artifacts"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_4","uri":"capability://text.generation.language.wiki.article.creation.and.editing","name":"wiki article creation and editing","description":"Allows developers to create, edit, and delete wiki articles stored in Dataiku DSS directly from VS Code, treating wiki articles as plain text files that sync bidirectionally with the DSS instance. The extension handles wiki article persistence through the DSS REST API while leveraging VS Code's native text editing capabilities.","intents":["I want to document my DSS projects and recipes using the built-in wiki without switching to the web UI","I need to version-control wiki articles alongside my code recipes","I want to use VS Code's markdown editing features for wiki documentation"],"best_for":["data teams documenting data pipelines and recipes in DSS","organizations using DSS wiki as a knowledge base for data governance","developers who prefer markdown editing in VS Code over web-based wiki editors"],"limitations":["Wiki articles are treated as plain text — no rich formatting preview in VS Code (requires markdown extension for preview)","No conflict resolution if wiki articles are edited simultaneously in VS Code and DSS web UI","Wiki article metadata (creation date, author, version history) is not accessible from VS Code","Cannot organize wiki articles into nested folders or categories — flat structure only"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with wiki write permissions","Network connectivity to DSS instance"],"input_types":["Plain text (markdown or plain text wiki content)"],"output_types":["Wiki article files (persisted to DSS)","Wiki article metadata (if available via API)"],"categories":["text-generation-language","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_5","uri":"capability://automation.workflow.plugin.file.and.folder.management.with.context.menu.operations","name":"plugin file and folder management with context menu operations","description":"Provides context menu operations (add, edit, delete) for managing plugin files and folders within DSS plugins, allowing developers to create new plugin components, modify existing files, and remove obsolete code without using the DSS web UI. The extension uses the DSS REST API to perform file system operations on the remote plugin directory structure.","intents":["I want to add new Python or JavaScript files to my DSS plugins from VS Code","I need to delete or rename plugin files without navigating the DSS web UI","I want to organize my plugin code into folders and manage the structure"],"best_for":["plugin developers building custom DSS extensions","teams maintaining multiple DSS plugins with complex file structures","developers who want to manage plugin code entirely within VS Code"],"limitations":["File operations are limited to plugins — cannot manage non-plugin DSS artifacts through this interface","No batch operations (e.g., bulk delete, bulk rename) — must perform operations one file at a time","Folder creation/deletion may not be supported; documentation is unclear on folder-level operations","No conflict resolution for simultaneous edits in VS Code and DSS web UI plugin editor"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with plugin write permissions","Network connectivity to DSS instance","Existing plugin in DSS instance"],"input_types":["File paths (for add/delete operations)","File content (for new files)"],"output_types":["Plugin file structure (updated in DSS)","Confirmation of file operations"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_6","uri":"capability://tool.use.integration.multi.instance.dss.configuration.with.environment.variable.and.config.file.support","name":"multi-instance dss configuration with environment variable and config file support","description":"Supports configuration of multiple Dataiku DSS instances through environment variables, a JSON configuration file (~/.dataiku/config.json), or VS Code command palette, allowing developers to switch between different DSS environments (dev, staging, production) without reconfiguring the extension. The extension reads configuration from environment variables first, then falls back to the config file, with a designated default instance for operations.","intents":["I want to work with multiple DSS instances (dev, staging, production) from the same VS Code workspace","I need to configure DSS connection details without hardcoding them in the extension settings","I want to use environment variables for CI/CD or containerized development environments"],"best_for":["teams with multiple DSS environments (dev, staging, production)","developers using containerized development environments or CI/CD pipelines","organizations with strict credential management policies requiring environment variable-based configuration"],"limitations":["Configuration file (~/.dataiku/config.json) is stored in plaintext — API keys are not encrypted, creating security risks if the file is exposed","No built-in credential rotation or expiration management — API keys must be manually updated","Multi-instance support requires manual selection of the default instance; no per-workspace or per-project instance selection","Environment variable names are fixed (DKU_DSS_URL, DKU_API_KEY) — no support for custom variable names or multiple instances via environment variables"],"requires":["Dataiku DSS instance URLs (http(s)://HOST:PORT format)","Valid personal API keys for each DSS instance","Write access to ~/.dataiku/config.json (for config file method)","Ability to set environment variables (for environment variable method)"],"input_types":["DSS instance URL (string)","Personal API key (string)","Instance name (string, for multi-instance config)"],"output_types":["Configuration file (JSON)","Environment variables (if using env var method)","Active DSS instance context (for extension operations)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_7","uri":"capability://tool.use.integration.command.palette.integration.for.dss.configuration.and.operations","name":"command palette integration for dss configuration and operations","description":"Exposes DSS-related operations through VS Code's command palette, including commands to configure DSS API credentials, set DSS instance URL, and trigger recipe execution. This allows developers to perform DSS operations without navigating menus or using keyboard shortcuts, following VS Code's standard command-driven UX paradigm.","intents":["I want to configure my DSS connection using VS Code's command palette instead of editing config files","I need quick access to DSS operations without remembering keyboard shortcuts","I want to discover available DSS commands by searching the command palette"],"best_for":["VS Code power users familiar with command palette workflows","teams using VS Code's command palette for all IDE operations","developers who prefer discoverability through search over menu navigation"],"limitations":["Command palette is text-based — no visual feedback for configuration options or available instances","No command history or recent commands feature documented — must search for commands each time","Limited to simple operations (configuration, execution) — complex workflows may require multiple command palette invocations"],"requires":["VS Code (version not specified)","Knowledge of DSS command names or ability to search for them"],"input_types":["Command name (string, via command palette search)","Configuration parameters (DSS URL, API key)"],"output_types":["Configuration updates (persisted to config file or environment)","Command execution results (logs, status)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_8","uri":"capability://automation.workflow.ssl.certificate.verification.configuration.for.local.recipe.execution","name":"ssl certificate verification configuration for local recipe execution","description":"Provides configuration options to enable or disable SSL certificate verification when executing recipes locally, allowing developers to work with DSS instances using self-signed certificates or in development environments with certificate issues. The extension passes SSL verification settings to the local Python/R execution environment.","intents":["I want to test recipes locally against a DSS instance with a self-signed certificate","I need to disable SSL verification for development environments without valid certificates","I want to configure SSL behavior without modifying system-wide certificate settings"],"best_for":["developers working with development or staging DSS instances using self-signed certificates","teams in environments with corporate proxies or certificate interception","developers who need flexibility in SSL configuration without system-wide changes"],"limitations":["Disabling SSL verification reduces security and should only be used in development environments","Configuration is global for the extension — cannot set different SSL settings per DSS instance","No support for custom certificate authorities (CA) — only binary enable/disable","SSL configuration only applies to local execution; remote execution SSL behavior is determined by DSS instance configuration"],"requires":["Local Python or R environment with dataiku package","VS Code extension settings access"],"input_types":["Boolean flag (SSL verification enabled/disabled)"],"output_types":["SSL verification configuration (applied to local execution environment)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-dataiku-dataiku-dss__cap_9","uri":"capability://automation.workflow.status.bar.integration.for.recipe.execution.control","name":"status bar integration for recipe execution control","description":"Displays a button in VS Code's bottom status bar that triggers remote recipe execution on the connected DSS instance, providing a single-click interface for executing the currently-open recipe file. The status bar button integrates with the remote execution capability, allowing developers to test recipes without opening menus or using command palette.","intents":["I want a quick one-click way to execute my recipe without using the command palette","I need visible feedback that recipe execution is available for the current file","I want to trigger recipe execution while keeping my focus on the editor"],"best_for":["developers who prefer UI buttons over command palette for frequent operations","teams with rapid iteration workflows requiring quick recipe execution","developers who benefit from visual affordances for available actions"],"limitations":["Status bar space is limited — button may be hidden if many extensions add status bar items","Button is always visible regardless of file type — may be confusing if non-recipe files are open","No visual feedback for execution status (running, completed, failed) — must check output window","Button location in status bar is not customizable"],"requires":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with recipe execution permissions","Network connectivity to DSS instance"],"input_types":["Current recipe file (implicit from editor context)"],"output_types":["Execution trigger (sent to DSS instance)","Execution logs (displayed in output window)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":40,"verified":false,"data_access_risk":"high","permissions":["Dataiku DSS instance version 6.0.0 or above","Valid personal API key with access to target DSS instance","VS Code (version not specified in documentation)","Network connectivity to configured DSS instance URL","Valid personal API key with recipe execution permissions","Network connectivity to DSS instance","Recipe must be valid and executable on the DSS instance","Recipe execution triggered via status bar button or command","Python 3.x with dataiku package installed locally (for Python recipes)","R with dataiku package installed locally (for R recipes)"],"failure_modes":["Requires DSS instance version 6.0.0 or higher; feature availability varies by DSS version","Bidirectional sync is file-level only — no conflict resolution for simultaneous edits in VS Code and DSS web UI","Cannot edit non-code DSS artifacts (datasets, flows, visual recipes) — only code recipes, libraries, and plugins","Network latency on recipe save depends on DSS instance responsiveness; no offline editing capability","Execution happens on the remote DSS instance, not locally — requires network connectivity and DSS availability","No built-in timeout or cancellation mechanism documented; long-running recipes may block the extension","Log streaming is unidirectional (server to client only) — cannot send input to running recipes","Execution context is limited to the DSS instance's environment; cannot access local files or environment variables","Log streaming is unidirectional (server to client) — cannot send input to running recipes or interact with the execution","Polling-based log updates may have latency; real-time streaming is not guaranteed","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.4,"quality":0.32,"ecosystem":0.35000000000000003,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.118Z","last_scraped_at":"2026-05-03T15:20:31.090Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=dataiku-dss","compare_url":"https://unfragile.ai/compare?artifact=dataiku-dss"}},"signature":"y+R57kEXK1tuY7GtYqT+y0YtyrePin30Nz8zGFKvaUrxMArvw4uEu7wBGfqgj6ilaSkBdaYEbEGbfUmJsvvJBQ==","signedAt":"2026-06-17T12:06:02.836Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/dataiku-dss","artifact":"https://unfragile.ai/dataiku-dss","verify":"https://unfragile.ai/api/v1/verify?slug=dataiku-dss","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}