search

catalyst-cooperative / pudl-usage-metrics

A dagster ETL for collecting and cleaning PUDL usage metrics.
MIT License
1 stars 0 forks source link

Bump dagit from 0.14.9 to 0.14.20 #17

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps dagit from 0.14.9 to 0.14.20.

Release notes

Sourced from dagit's releases.

0.14.20 (June 9, 2022)

New

  • [dagster-aws] Added an env_vars field to the EcsRunLauncher that allows you to configure environment variables in the ECS task for launched runs.
  • [dagster-k8s] The env_vars field on K8sRunLauncher and k8s_job_executor can now except input of the form ENV_VAR_NAME=ENV_VAR_VALUE, and will set the value of ENV_VAR_NAME to ENV_VAR_VALUE. Previously, it only accepted input of the form ENV_VAR_NAME, and the environment variable had to be available in the pod launching the job.
  • [dagster-k8s] setting ‘includeConfigInLaunchedRuns’ on a user code deployment will now also include any image pull secrets from the user code deployment in the pod for the launched runs.

Bugfixes

  • A recent change had made it so that, when IOManager.load_input was called to load an asset that was not being materialized as part of the run, the provided context would not include the metadata for that asset. context.upstream_output.metadata now correctly returns the metadata on the upstream asset.
  • Fixed an issue where using generic type aliases introduced in Python 3.9 (like list[str]) as the type of an input would raise an exception.
  • [dagster-k8s] Fixed an issue where upgrading the Helm chart version without upgrading your user code deployment version would result in an “Received unexpected config entry "scheme" at path root:postgres_db" error.

All Changes

https://github.com/dagster-io/dagster/compare/0.14.19...0.14.20

  • b6cf5d2 - 0.14.20rc0 by @​elementl-devtools
  • d421a1b - Fixes for asset graphql tests to make them easier to generalize and call with other graphql context fixtures ([#8199](https://github.com/dagster-io/dagster/issues/8199)) by @​gibsondan
  • 58fa8ca - bring back source asset metadata ([#8195](https://github.com/dagster-io/dagster/issues/8195)) by @​sryza
  • 561b81a - fix is_subclass bug where issubclass(list[str], DagsterType) throws a surprising exception ([#8287](https://github.com/dagster-io/dagster/issues/8287)) by @​gibsondan
  • de28811 - Add max_retries to user editable tags ([#8285](https://github.com/dagster-io/dagster/issues/8285)) by @​johannkm
  • 37d0062 - Derive origin from pipeline run instead of the arg to ExecuteRunArgs ([#8156](https://github.com/dagster-io/dagster/issues/8156)) by @​gibsondan
  • cb800cc - add an "environment" key to EcsRunLauncher / EcsContainerContext that sets env vars ([#8243](https://github.com/dagster-io/dagster/issues/8243)) by @​gibsondan
  • ed1b9b0 - Fix upgrade story for new scheme field in postgres ([#8220](https://github.com/dagster-io/dagster/issues/8220)) by @​gibsondan
  • 455fb97 - Add image pull secrets to k8s container context ([#8221](https://github.com/dagster-io/dagster/issues/8221)) by @​gibsondan
  • d1319e2 - extract event connection to top-level graphql query ([#8077](https://github.com/dagster-io/dagster/issues/8077)) by @​prha
  • 5e2badf - Create unified storage configuration for dagster.yaml ([#7283](https://github.com/dagster-io/dagster/issues/7283)) by @​prha
  • 601a9cb - [dagster-dbt] Fix bug where a dbt invocation that did not successfully start could emit materialization events. ([#8293](https://github.com/dagster-io/dagster/issues/8293)) by @​OwenKephart
  • aa5d8ca - Move config editor to core so we can reuse in admin portal ([#8237](https://github.com/dagster-io/dagster/issues/8237)) by @​salazarm
  • 8f9294a - Make dagster/reexecution_strategy tag editable ([#8286](https://github.com/dagster-io/dagster/issues/8286)) by @​johannkm
  • 2a8d755 - only return config field for solids ([#8278](https://github.com/dagster-io/dagster/issues/8278)) by @​clairelin135
  • 5f13fcd - clean up create_pg_connection ([#8165](https://github.com/dagster-io/dagster/issues/8165)) by @​alangenfeld
  • b6c65e4 - 0.14.20 Changelog ([#8301](https://github.com/dagster-io/dagster/issues/8301)) by @​johannkm
  • a44bb67 - 0.14.20 by @​elementl-devtools

0.14.19 (June 3, 2022)

New

  • Metadata can now be added to jobs (via the metadata parameter) and viewed in dagit. You can use it to track code owners, link to docs, or add other useful information.
  • In the Dagit launchpad, the panel below the config editor now shows more detailed information about the state of the config, including error state and whether the config requires further scaffolding or the removal of extra config.
  • FileCache is now marked for deprecation in 0.15.0.
  • In Dagit, the asset catalog now shows the last materialization for each asset and links to the latest run.
  • Assets can now have a config_schema. If you attempt to materialize an asset with a config schema in Dagit, you'll be able to enter the required config via a modal.

Bugfixes

... (truncated)

Changelog

Sourced from dagit's changelog.

0.14.20

New

  • [dagster-aws] Added an env_vars field to the EcsRunLauncher that allows you to configure environment variables in the ECS task for launched runs.
  • [dagster-k8s] The env_vars field on K8sRunLauncher and k8s_job_executor can now except input of the form ENV_VAR_NAME=ENV_VAR_VALUE, and will set the value of ENV_VAR_NAME to ENV_VAR_VALUE. Previously, it only accepted input of the form ENV_VAR_NAME, and the environment variable had to be available in the pod launching the job.
  • [dagster-k8s] setting ‘includeConfigInLaunchedRuns’ on a user code deployment will now also include any image pull secrets from the user code deployment in the pod for the launched runs.

Bugfixes

  • A recent change had made it so that, when IOManager.load_input was called to load an asset that was not being materialized as part of the run, the provided context would not include the metadata for that asset. context.upstream_output.metadata now correctly returns the metadata on the upstream asset.
  • Fixed an issue where using generic type aliases introduced in Python 3.9 (like list[str]) as the type of an input would raise an exception.
  • [dagster-k8s] Fixed an issue where upgrading the Helm chart version without upgrading your user code deployment version would result in an “Received unexpected config entry "scheme" at path root:postgres_db" error.

0.14.19

New

  • Metadata can now be added to jobs (via the metadata parameter) and viewed in dagit. You can use it to track code owners, link to docs, or add other useful information.
  • In the Dagit launchpad, the panel below the config editor now shows more detailed information about the state of the config, including error state and whether the config requires further scaffolding or the removal of extra config.
  • FileCache is now marked for deprecation in 0.15.0.
  • In Dagit, the asset catalog now shows the last materialization for each asset and links to the latest run.
  • Assets can now have a config_schema. If you attempt to materialize an asset with a config schema in Dagit, you'll be able to enter the required config via a modal.

Bugfixes

  • [helm] Fixed an issue where string floats and integers were not properly templated as image tags.
  • [dagster-k8s] Fixed an issue when using the k8s_job_executor where ops with long names sometimes failed to create a pod due to a validation error with the label names automatically generated by Dagster.
  • [dagster-aws] Fixed an issue where ECS tasks with large container contexts would sometimes fail to launch because their request to the ECS RunTask API was too large.

Breaking Changes

  • fs_asset_io_manager has been removed in favor of merging its functionality with fs_io_manager. fs_io_manager is now the default IO manager for asset jobs, and will store asset outputs in a directory named with the asset key.

Community Contributions

  • Fixed a bug that broke the k8s_job_executor’s max_conccurent configuration. Thanks @​fahadkh!
  • Fixed a bug that caused the fs_io_manager to incorrectly handle assets associated with upstream assets. Thanks @​aroig!

Documentation

  • [helm] Add documentation for code server image pull secrets in the main chart.
  • The Dagster README has been revamped with documentation and community links.

0.14.17

New

... (truncated)

Commits
  • a44bb67 0.14.20
  • b6c65e4 0.14.20 Changelog (#8301)
  • 5f13fcd clean up create_pg_connection (#8165)
  • 2a8d755 only return config field for solids (#8278)
  • 8f9294a Make dagster/reexecution_strategy tag editable (#8286)
  • aa5d8ca Move config editor to core so we can reuse in admin portal (#8237)
  • 601a9cb [dagster-dbt] Fix bug where a dbt invocation that did not successfully start ...
  • 5e2badf Create unified storage configuration for dagster.yaml (#7283)
  • d1319e2 extract event connection to top-level graphql query (#8077)
  • 455fb97 Add image pull secrets to k8s container context (#8221)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

The following labels could not be found: dependencies.

dependabot[bot] commented 2 years ago

Superseded by #24.