The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hey all, I was looking into using some of the capabilities within dagster_shell but wanted to use <https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-shell/dagster_shell/utils.py#L118|the >`execute`<https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-shell/dagster_shell/utils.py#L118| function> called <https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-shell/dagster_shell/solids.py#L67|by >`shell_op`  directly in a regular op. Out of curiosity, would I be safe in consuming this function or is `dagster_shell.utils.execute` not considered a public API?

cc <@U01GTMVMGQH> / <@U017KUAENS0> re: public API audit

If it's not exported from the top-level of the module, or in the API docs directly, then it wouldn't be considered a public API. If you find that function useful enough though, could make a case for including it/something similar in the public API

Awesome, thanks. What might the process for making it public look like? Should I submit a PR exporting it from the top level + add docs?

Before making a PR, I would make an issue around it as a forum for discussion, and we can decide whether to move forward

Sweet, submitted an issue <https://github.com/dagster-io/dagster/issues/8879>. Thanks for your help Chris!