Johann Miller
Johann Miller
### Discussed in https://github.com/dagster-io/dagster/discussions/8001 Originally posted by **Tehada** May 21, 2022 According to [docs](https://docs.dagster.io/deployment/guides/kubernetes/customizing-your-deployment), we can specify resources for op's pod using syntax below: ```python @op( tags={ "dagster-k8s/config": { "container_config":...
We only test using one release of the separate user-code-deployment chart. Unclear if things would work when running multiple. Test this out
### What's the use case? Currently automatic run retries https://docs.dagster.io/deployment/run-retries trigger on any run failure. Add a setting to only trigger when a system failure occurs, rather than an exception...
Snippets like https://app.graphite.dev/github/pr/dagster-io/dagster/8117 would be useful for docs, but we don't have a place to put them
Moving https://github.com/dagster-io/dagster/discussions/17194 in to docs
Rough draft: - set FreshnessPolicy on source assets - freshness is calculated based on a `data_time` timestamp set in the AssetObservation metadata. There's currently no way to set that with...
Add coverage for this case
https://dagster.slack.com/archives/C02LJ7G0LAZ/p1696868420320779 If not using pex, don't require installing it
For consistency with build_column_schema_change_checks
Add an experimental `build_metadata_range_checks` factory for asserting that a numeric metadata value is within a range. ```python @asset def my_asset(): return MaterializeResult(metadata={"my_metadata": 5}) checks = build_metadata_range_checks( assets=[my_asset], metadata_key="my_metadata", min_value=1, max_value=10...