Roei Jacobovich
06/15/2022, 7:14 AMdagster-k8s/config
tag to all the Ops without decorating/editing each @op
? Seems like the dagster-k8s/config
tag on the job itself applied to the dagster-run
K8s job only, and not to every dagster-step
k8s job being executed.
(we’re using k8s_job_executor
and k8s_run_launcher
)
Also, is there a way to change the job executing binary? we’d like to run DataDog’s tracing utility (ddtrace_run
) and apply it before the actual Dagster command
Thanks 🙂daniel
06/15/2022, 1:42 PMdef op_with_default_tags(*args, **kwargs):
kwargs["tags"] = {**kwargs.get("tags", {}), **{"foo": "bar"}}
return op(*args, **kwargs)
@op_with_default_tags()
def your_op(foo):
return foo + 1
daniel
06/15/2022, 1:53 PMStephen Bailey
06/20/2022, 7:51 PM@mycompany_job
decorator that applies default k8s tags, as well as hooks, etc. : https://dagster.slack.com/archives/C01U5LFUZJS/p1654881409811469Roei Jacobovich
07/02/2022, 4:06 PMddtrace-run
for anybody else searching for that: we changed the Dockerfile’s ENTRYPOINT
(to ENTRYPOINT ["ddtrace-run"]
) as Daniel suggested, and added DD_TRACE_ENABLED=FALSE
as env for local development to avoid errors.
Thanks 🙂