fix(dagster): Update dagster (patch) #180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==0.20.5
->==0.20.6
==0.20.5
->==0.20.6
1.4.5
->1.4.6
Release Notes
dagster-io/dagster (dagster-azure)
v0.20.6
New
None
/Nothing
will interpret an explicitly or implicitly returned valueNone
to indicate that all outputs were successful.skip_reason
argument to the constructor ofSensorResult
now accepts a string in addition to aSkipReason
.step_k8s_config
field tok8s_job_executor
that allows you to customize the raw Kubernetes config for each step in a job. See the docs for more information.dagster-dbt project scaffold
now creates the scaffold in multiple files:constants.py
contains a reference to your manifest and dbt project directoryassets.py
contains your initial dbt assets definitionsdefinitions.py
contains the code to load your asset definitions into the Dagster UIschedules.py
contains an optional schedule to add for your dbt assetsget_auto_materialize_policy
andget_freshness_policy
toDagsterDbtTranslator
.load_assets_from_fivetran_instance
.Bugfixes
SSHResource
would warn whenallow_host_key_change
was set. Now known hosts are always loaded from the system hosts file, and theallow_host_key_change
parameter is ignored.Documentation
@graph_multi_asset
now has an API docs entry.GCSComputeLogManager
example in the Dagster Instance reference is now correct.@dbt_assets
for the following use-cases:--vars
Dagster Cloud
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.