Dagster-cloud

New

- Added [Terms of Service](https://dagster.io/terms) to Dagster Cloud.
- Organization admins can now be managed from the Cloud permissions page. For more information, see the Cloud [RBAC docs](https://docs.dagster.cloud/auth#role-based-access-controls).

Bugfixes

- Fixed an issue where an empty list of email addresses could be configured on an email alert policy.
- When an agent is accidentally configured with a user token rather than an agent token, an informative exception is now displayed.
- Fixed an issue where jobs using [memoization](https://docs.dagster.io/guides/dagster/memoization#versioning-and-memoization) sometimes did not launch in Dagster Cloud.

New

- The new features announced in the [Dagster 0.15.0 release](https://github.com/dagster-io/dagster/releases/tag/0.15.0) are also available to Dagster Cloud users. In particular, software-defined assets are now marked fully stable and are ready for prime time - we recommend using them whenever your goal using Dagster is to build and maintain data assets.
- The [ECS agent CloudFormation template](https://docs.dagster.cloud/agents/ecs/setup#provisioning-using-cloudformation) is now versioned, allowing you to fix a specific version of the agent.
- You can now configure job-level retries to re-execute the full run rather than just failed Ops by setting the `dagster/retry_strategy` tag to `ALL_STEPS`. See [the docs](https://docs.dagster.io/deployment/run-retries) for more information.

New

- The Kubernetes agent and ECS agent can now include arbitrary environment variables in the containers that they create to run Dagster code. You can configure environment variables by setting `env_vars` in the `dagster.yaml` file for the agent, which will apply them to all code locations. You can also set `env_vars` on individual code locations. For example, to configure a code location to always set `FOO_ENV_VAR` to `bar_value` when creating Kubernetes pods, you can set this config in the Workspace tab or via the Dagster Cloud GitHub action:

yaml
location_name:my_location
image: my_repo:my_tag
code_source:
package_name: my_package
container_context:
k8s:
env_vars:
- FOO_ENV_VAR=bar_value
- WILL_LOAD_ENV_VAR_FROM_PROCESS_IF_VALUE_NOT_SET


- Introduced a checklist to guide new organizations in setting up their Cloud deployment.

- Users with Editor or Admin permissions can now edit [deployment settings](https://docs.dagster.cloud/guides/managing-deployments#deployment-settings) from the Dagster Cloud UI, by clicking on the gear icon next to the deployment name in the deployment switcher in the upper-right corner of the screen.

Bugfixes

- Fixed a bug where renaming an alert created a new alert.
- Attempting to create a deployment with a duplicate name now produces a clear error.

New

- Added a new `dagster-cloud-cli` package. You can install this package if you want to interact with the CLI without also installing many of the additional packages that `dagster-cloud` depends on, simplifying installation on M1 Macs.
- [Deployment settings](https://docs.dagster.cloud/guides/managing-deployments#deployment-settings) can now be configured using a YAML editor in the Dagster Cloud UI.

Bugfixes

- Fixed an issue where a user could set their run coordinator’s `max_concurrent_runs` to be negative.
- [dagit] Alerts can now be configured on a deployment with no jobs.

New

- The Backfill page in Dagit now loads much faster when there are backfills with large numbers of runs.

Bugfixes

- Added a pin to version 3 of the `protobuf` library in Dagster Cloud, due to a breaking change in version 4 that was causing an error on startup.
- Fixed an issue where configuration errors while launching a run sometimes didn’t display a useful explanation for why the configuration was invalid.
- Fixed an issue where Dagster Cloud would sometimes fail to fire failure alerts due to external rate limits.