-
Notifications
You must be signed in to change notification settings - Fork 93
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
schema: separate task and job mutations #3880
schema: separate task and job mutations #3880
Conversation
""" | ||
|
||
|
||
class NamespaceJobGlob(String): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This input type enables us to tell that this mutation works on jobs by flicking through the results of an introspection query.
71bdab7
to
88bb726
Compare
) | ||
|
||
|
||
def parse_reference(string): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This replaces TaskPool._parse_task_item
.
88bb726
to
ff98960
Compare
ff98960
to
5ca1c85
Compare
Closing this now, will bring back in a new form with the universal identifier. |
Separate task and job mutations in the schema.
At present there isn't much value to being able to specify a particular job submit number since it would be considered an error for two jobs to run at the same time.
Here's an example specifying the job submit num on the CLI:
And here via GraphQL:
Obviously
#
isn't ideal for use on the CLI, we could consider something else, see also #3592.Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.setup.py
, seerecipe/meta.yaml
).