With the dagster 1.0 release and the new public/pr...
# ask-community
a
With the dagster 1.0 release and the new public/private API split, are there plans to more fully support custom executors? The docs still suggest that using internal APIs is the way to go. Looks like about half the imports for my custom executor are available from the public package, but the other half need to still be imported via the private API packages. (fwiw, my executor case is basically just a subclassed standard executor with a post execution hook for istio compatibility)
a
are there plans to more fully support custom executors?
Not at this time. We are likely to make some changes to how execution is modeled between now and 2.0 so we are not ready to commit to those APIs yet.