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]: add support for removing executors from configuration file #1609

Closed
2 tasks done
shahzebsiddiqui opened this issue Aug 30, 2023 · 0 comments · Fixed by #1636
Closed
2 tasks done

[FEATURE]: add support for removing executors from configuration file #1609

shahzebsiddiqui opened this issue Aug 30, 2023 · 0 comments · Fixed by #1636
Assignees

Comments

@shahzebsiddiqui
Copy link
Member

Please describe your feature

add support in buildtest to remove executors via command line.

We can introduce a command name buildtest config executors remove which takes positional argument to remove executors by name.

Let's say we have the following executors as shown below

(buildtest)  ~/Documents/github/buildtest/ [devel*] buildtest cg executors   
generic.local.sh
generic.local.csh
generic.local.zsh

If we want to remove the zsh executor we could do buildtest config executors remove generic.local.zsh and this will remove the section for zsh which would be the section for zsh under the executors section

(buildtest)  ~/Documents/github/buildtest/ [devel*] buildtest cg executors -y
executors:
  local:
    bash:
      description: submit jobs on local machine using bash shell
      shell: 123bash
    csh:
      description: submit jobs on local machine using csh shell
      shell: csh
    sh:
      description: submit jobs on local machine using sh shell
      shell: sh
    zsh:
      description: submit jobs on local machine using zsh shell
      shell: zsh

Suggest potential solution

No response

Additional Information

No response

Post question in Slack

  • I agree that I posted my question in slack before creating this issue

Is there an existing issue

  • I confirm there is no existing issue for this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant