Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature-request] Use Custom CommandExecutors #901

Closed
muga opened this issue Oct 18, 2018 · 1 comment · Fixed by #1681
Closed

[feature-request] Use Custom CommandExecutors #901

muga opened this issue Oct 18, 2018 · 1 comment · Fixed by #1681

Comments

@muga
Copy link
Member

muga commented Oct 18, 2018

Some users request the option for using their custom CommandExecutor to execute command operator e.g. py>, rb>. They want to execute the operators on different place from Digdag where are running. Currently we don't have any extension point to load custom CommandExecutor and specify it for command operators.

@muga muga added this to the v0.10.0 milestone Oct 18, 2018
@civitaspo
Copy link
Contributor

I wrote Scripting Operators without custom CommandExecutors. > https://github.com/civitaspo/digdag-operator-ecs_task#experimental-scripting-operators
This is what I wanted to do. When the CommandExecutor can be implemented, we will reimplement these Scripting Operators.

@yoyama yoyama modified the milestones: v0.10.0, v0.10.1 Jan 26, 2021
@szyn szyn modified the milestones: v0.10.1, v0.10.2 Jun 3, 2021
@szyn szyn modified the milestones: v0.10.2, v0.10.3 Jul 22, 2021
@szyn szyn modified the milestones: v0.10.3, v0.10.4 Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants