Bump dagster-fivetran from 0.24.9 to 0.24.10

[dependabot]

Bumps dagster-fivetran from 0.24.9 to 0.24.10.

Release notes

Sourced from dagster-fivetran's releases.

1.8.10 (core) / 0.24.10 (libraries)

New

• JobDefinition, @job, and define_asset_job now take a run_tags parameter. If run_tags are defined, they will be attached to all runs of the job, and tags will not be. If run_tags is not set, then tags are attached to all runs of the job (status quo behavior). This change enables the separation of definition-level and run-level tags on jobs.
• Then env var DAGSTER_COMPUTE_LOG_TAIL_WAIT_AFTER_FINISH can now be used to pause before capturing logs (thanks @​HynekBlaha!)
• The kinds parameter is now available on AssetSpec.
• OutputContext now exposes the AssetSpec of the asset that is being stored as an output (thanks, @​marijncv!)
• [experimental] Backfills are incorporated into the Runs page to improve observability and provide a more simplified UI. See the GitHub discussion for more details.
• [ui] The updated navigation is now enabled for all users. You can revert to the legacy navigation via a feature flag. See GitHub discussion for more.
• [ui] Improved performance for loading partition statuses of an asset job.
• [dagster-docker] Run containers launched by the DockerRunLauncher now include dagster/job_name and dagster/run_id labels.
• [dagster-aws] The ECS launcher now automatically retries transient ECS RunTask failures (like capacity placement failures).

Bugfixes

• Changed the log volume for global concurrency blocked runs in the run coordinator to be less spammy.
• [ui] Asset checks are now visible in the run page header when launched from a schedule.
• [ui] Fixed asset group outlines not rendering properly in Safari.
• [ui] Reporting a materialization event now removes the asset from the asset health "Execution failures" list and returns the asset to a green / success state.
• [ui] When setting an AutomationCondition on an asset, the label of this condition will now be shown in the sidebar on the Asset Details page.
• [ui] Previously, filtering runs by Created date would include runs that had been updated after the lower bound of the requested time range. This has been updated so that only runs created after the lower bound will be included.
• [ui] When using the new experimental navigation flag, added a fix for the automations page for code locations that have schedules but no sensors.
• [ui] Fixed tag wrapping on asset column schema table.
• [ui] Restored object counts on the code location list view.
• [ui] Padding when displaying warnings on unsupported run coordinators has been corrected (thanks @​hainenber!)
• [dagster-k8s] Fixed an issue where run termination sometimes did not terminate all step processes when using the k8s_job_executor, if the termination was initiated while it was in the middle of launching a step pod.

Documentation

• Corrections on the Dagster instance concept page (thanks @​mheguy!)
• Corrections on the code locations concept page (thanks @​tiberiuana!)
• Repeated words removed (thanks @​tianzedavid!)
• [dagster-deltalake] Corrections and improvements (thanks @​avriiil!)
• [dagster-aws] Added docs for PipesEMRServerlessClient.
• [dagster-cli] A guide on how to validate Dagster definitions using dagster definitions validate have been added.
• [dagster-databricks] Added docs for using Databricks Pipes with existing clusters.
• [dagster-dbt] Corrected sample sql code (thanks @​b-per!)

1.8.9 (core) / 0.24.9 (libraries)

New

• AssetSpec now has a with_io_manager_key method that returns an AssetSpec with the appropriate metadata entry to dictate the key for the IO manager used to load it. The deprecation warning for SourceAsset now references this method.
• Added a max_runtime_seconds configuration option to run monitoring, allowing you to specify that any run in your Dagster deployment should terminate if it exceeds a certain runtime. Prevoiusly, jobs had to be individually tagged with a dagster/max_runtime tag in order to take advantage of this feature. Jobs and runs can still be tagged in order to override this value for an individual run.
• It is now possible to set both tags and a custom execution_fn on a ScheduleDefinition. Schedule tags are intended to annotate the definition and can be used to search and filter in the UI. They will not be attached to run requests emitted from the schedule if a custom execution_fn is provided. If no custom execution_fn is provided, then for back-compatibility the tags will also be automatically attached to run requests emitted from the schedule.
• SensorDefinition and all of its variants/decorators now accept a tags parameter. The tags annotate the definition and can be used to search and filter in the UI.
• Added the dagster definitions validate command to Dagster CLI. This command validates if Dagster definitions are loadable.
• [dagster-databricks] Databricks Pipes now allow running tasks in existing clusters.

Bugfixes

... (truncated)

Changelog

Sourced from dagster-fivetran's changelog.

1.8.10 (core) / 0.24.10 (libraries)

New

• JobDefinition, @job, and define_asset_job now take a run_tags parameter. If run_tags are defined, they will be attached to all runs of the job, and tags will not be. If run_tags is not set, then tags are attached to all runs of the job (status quo behavior). This change enables the separation of definition-level and run-level tags on jobs.
• Then env var DAGSTER_COMPUTE_LOG_TAIL_WAIT_AFTER_FINISH can now be used to pause before capturing logs (thanks @​HynekBlaha!)
• The kinds parameter is now available on AssetSpec.
• OutputContext now exposes the AssetSpec of the asset that is being stored as an output (thanks, @​marijncv!)
• [experimental] Backfills are incorporated into the Runs page to improve observability and provide a more simplified UI. See the GitHub discussion for more details.
• [ui] The updated navigation is now enabled for all users. You can revert to the legacy navigation via a feature flag. See GitHub discussion for more.
• [ui] Improved performance for loading partition statuses of an asset job.
• [dagster-docker] Run containers launched by the DockerRunLauncher now include dagster/job_name and dagster/run_id labels.
• [dagster-aws] The ECS launcher now automatically retries transient ECS RunTask failures (like capacity placement failures).

Bugfixes

• Changed the log volume for global concurrency blocked runs in the run coordinator to be less spammy.
• [ui] Asset checks are now visible in the run page header when launched from a schedule.
• [ui] Fixed asset group outlines not rendering properly in Safari.
• [ui] Reporting a materialization event now removes the asset from the asset health "Execution failures" list and returns the asset to a green / success state.
• [ui] When setting an AutomationCondition on an asset, the label of this condition will now be shown in the sidebar on the Asset Details page.
• [ui] Previously, filtering runs by Created date would include runs that had been updated after the lower bound of the requested time range. This has been updated so that only runs created after the lower bound will be included.
• [ui] When using the new experimental navigation flag, added a fix for the automations page for code locations that have schedules but no sensors.
• [ui] Fixed tag wrapping on asset column schema table.
• [ui] Restored object counts on the code location list view.
• [ui] Padding when displaying warnings on unsupported run coordinators has been corrected (thanks @​hainenber!)
• [dagster-k8s] Fixed an issue where run termination sometimes did not terminate all step processes when using the k8s_job_executor, if the termination was initiated while it was in the middle of launching a step pod.

Documentation

• Corrections on the Dagster instance concept page (thanks @​mheguy!)
• Corrections on the code locations concept page (thanks @​tiberiuana!)
• Repeated words removed (thanks @​tianzedavid!)
• [dagster-deltalake] Corrections and improvements (thanks @​avriiil!)
• [dagster-aws] Added docs for PipesEMRServerlessClient.
• [dagster-cli] A guide on how to validate Dagster definitions using dagster definitions validate have been added.
• [dagster-databricks] Added docs for using Databricks Pipes with existing clusters.
• [dagster-dbt] Corrected sample sql code (thanks @​b-per!)

Commits

• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Looks like dagster-fivetran is up-to-date now, so this is no longer needed.