Customizing Source Code Links in Asset Overview Pages

Last updated: October 31, 2025

Problem Description

  The "Open component.yaml in editor" link in the Asset Overview page's Source Code section points to local file paths that are not useful in production deployments. Users need these links to point to GitHub URLs for the deployed git commit instead of local development paths.

Symptoms

  • Source code links show deployment-specific paths like /venvs/936634c7408d/lib/python3.11/site-packages/working_directory/root/morpheus/defs/ise/component.yaml:37

  • Links don't work properly in production environments

  • Default IDE opening functionality fails due to incorrect file paths

Root Cause

  The default editor link protocol uses the full deployment path rather than the repository-relative path, making it unsuitable for linking to GitHub or other remote repositories in production environments.

Solution

  Customize the editor link protocol in user settings to point to your preferred URL format.

Step-by-Step Resolution

  1. Navigate to your user settings in the Dagster interface

  2. Find the "Editor link protocol" option (the last option in the settings)

  3. Configure the protocol to match your preferred URL format (e.g., GitHub, GitLab, etc.)

Alternative Solutions (if applicable)

  For production environments, you can wrap your assets with a method that swaps to github-based code references when in a production environment. This provides more granular control over code references per environment.

Prevention

  Set up environment-specific code reference configurations during initial deployment setup to ensure source code links work appropriately in both development and production environments.

Related Documentation