Dagster-cloud

New

- The ECS Agent now shares a single task definition for every code location (instead of one task definition for the code location and another for any runs originating from that code location)
- `dagster-cloud serverless deploy` now blocks until the code location loads instead of returning immediately. This brings its behavior in line with other commands in the CLI and makes it safer to chain together multiple commands in a row (like launching a job after you deploy) without first needing to check if the deploy was successful.
- The deferred job snapshots option for workspace updates is now defaulted to on.

Bugfixes

- [dagit] For users with the “New workspace page” feature flag enabled, code locations could not be added from the Deployment page. This has been fixed.

New

- The ECS agent can now run in ECS clusters using EC2 capacity providers. See the [ECS agent docs](https://docs.dagster.io/dagster-cloud/deployment/agents/amazon-ecs/creating-ecs-agent-existing-vpc) for more information.
- The CloudFormation template for the ECS agent now configures multi-AZ support for the containers it launches.
- The default amount of time that a Dagster Cloud agent waits for user code to import being timing out has been increased from 60 seconds to 180 seconds, to avoid false positives when loading code with heavy imports or large numbers of assets.
- Added a deployment setting to configure the default role for SAML-provisioned users.

Bugfixes

- The dagster-cloud CLI no longer lists branch deployments in the list of default deployments during setup.

Bugfixes

- The GitHub setup flow for Serverless will now display an error if Actions builds are blocked from starting due to GitHub permissions.

New

- When alerts are configured in Dagster Cloud on a job that also has automatic retries , the alert will now only fire if the final retry fails.
- Performance improvements to the Overview page.
- Job snapshot uploads now use a thread pool for parallelism.

Bugfixes

- Fixed an issue where links to the compute logs in Dagit would sometimes fail to load.
- Improved user-facing error messages for Serverless GitHub setup.

New

- Performance improvements for the Partitions page.
- A new scheme for workspaces updates has been added that improves performance in deployments with a large number of jobs. This is currently opt-in via the `defer_job_snapshots` setting in `user_code_launcher` config in dagster.yaml, or via `deferJobSnapshots` in the `workspace` section of the Dagster Cloud helm chart.

Bugfixes

- Fixed an issue where assets sometimes didn’t appear in the Asset Catalog while in Folder view.
- Fixed an issue where the Create Token button would erroneously appear when revoking other users’ tokens.

New

- [Kubernetes] Custom Kubernetes schedulers can now be applied to pods launched by the Dagster Cloud agent. To change the scheduler for all pods created by the agent, set `workspace.schedulerName` in the agent Helm chart. To set it for only the pods created as part of a particular code location, set the following configuration for the code location on the Workspace tab:


container_context:
k8s:
scheduler_name: your-custom-schedule-name


To change it for the agent, you'll still need to set `dagsterCloudAgent.schedulerName` in the agent Helm chart.

Bugfixes

- Fixed an issue where the “Latest run” column on the Instance Status page sometimes displayed an older run instead of the most recent run.
- Added a pin to grpcio to address an issue with the recent 0.48.1 grpcio release that was sometimes causing Dagster code servers to hang.