When running Dagster locally using

dagster dev

, is there a way to auto-reload the deployment whenever code in the workspace changes?

When running Dagster locally with

dagster dev

, the documentation does not explicitly mention an auto-reload feature that detects changes in the workspace and reloads the deployment automatically. However, the documentation does describe a "Reload All" button in the Deployment tab of the Dagster UI that can be used to manually reload all the definitions when you add new code locations to your

workspace.yaml

. This manual action allows the new definitions to be present without restarting the process. For production deployments, the documentation suggests using separate containers for code servers and mentions that the only way to reload definitions in such a setup is to restart the process, typically requiring a restart of the container or pod. If you are looking for an auto-reload feature during local development, you might consider using file system watchers or other development tools that can monitor file changes and trigger a reload command. However, this approach is not covered in the documentation and would be something you would need to set up independently of Dagster's built-in capabilities.