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

✨ Add patch support for /tasks and /taskgroups. #661

Closed
jortel opened this issue Jun 14, 2024 · 0 comments · Fixed by #660
Closed

✨ Add patch support for /tasks and /taskgroups. #661

jortel opened this issue Jun 14, 2024 · 0 comments · Fixed by #660
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/major Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@jortel
Copy link
Contributor

jortel commented Jun 14, 2024

Add patch for:

  • /tasks
  • /taskgroups

Example task patch to update the prempt policy: PATCH /tasks/:id
body (yaml):

policy:
  preemptEnabled: true

body (json):

{"policy": {"preemptEnabled": true}}
@jortel jortel added kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/major Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jun 14, 2024
@jortel jortel added this to the v0.5.0 milestone Jun 14, 2024
@jortel jortel self-assigned this Jun 14, 2024
@jortel jortel closed this as completed in ff2ba63 Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/major Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant