Dagster-cloud

New

- Performance improvements when the Dagster Cloud agent is deploying more than one code location at the same time.
- The default timeout for runs to start has been increased from 5 minutes to 10 minutes. We had observed that ECS tasks often would exceed timeout when pulling a large image.

New

- Branch Deployments are now ordered by their most recent commit time on the Deployments tab.
- You can now access the name of the current Dagster Cloud deployment within your Dagster code by checking the `DAGSTER_CLOUD_DEPLOYMENT_NAME` environment variable. You can use this to change the behavior of your code depending on the deployment in which it is running.

Bugfixes

- Fixed an issue where launching a run with just whitespace in the Launchpad would create an error.
- Fixed an issue where creating a code location that started with a numeric character failed to load when using the Kubernetes agent.

New

- Improved query performance for loading the Asset Graph in Dagit.
- The ECS agent is now more resilient to ECS’s eventual consistency model. In your dagster.yaml, you can configure how long ECS polls against AWS ECS API endpoints by setting:


user_code_launcher:
module: dagster_cloud.workspace.ecs
class: EcsUserCodeLauncher
config:
timeout: 180 default: 300


And you can configure how long ECS will retry a failed AWS ECS API endpoint by setting:


user_code_launcher:
module: dagster_cloud.workspace.ecs
class: EcsUserCodeLauncher
config:
grace_period: 20 default: 10


- The Dagster Cloud API may start returning HTTP response code 429 when it receives an unusually large number of requests in a short period of time. The HTTP response will include a `Retry-After` header indicating the number of seconds to wait before retrying the request.

Bugfixes

- Fixed an issue where the Kubernetes agent didn’t work correctly when setting `container_context.namespace` to run code locations in different Kubernetes namespaces.

New

- The dagster-cloud CLI now supports adding a single code location from a file containing a list of locations by specifying the `--location-name` parameter.

New

- User code servers now support a configurable time-to-live (TTL). The agent will spin down any user code servers that haven’t served requests recently and will spin them back up the next time they’re needed. You can use this TTL to save compute cost because your user code servers will spend less time sitting idle. [You can configure TTL](https://docs.dagster.cloud/agents/agent-settings#enabling-user-code-server-ttl) in your agent’s `dagster.yaml`:

yaml
user_code_launcher:
config:
server_ttl:
enabled: true
ttl_seconds: 7200 2 hours


- When viewing agent and user tokens under the settings page, tokens are now sorted by latest creation date.

Bugfixes

- When configuring alert policies, all inputs are now validated before submission.
- When copying an agent related error message, the original error and stack trace are now included.