-
Notifications
You must be signed in to change notification settings - Fork 13
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
[teraslice-cli] add earl jobs export command #3717
Conversation
8eb853a
to
3b30034
Compare
I would think the current directory makes more sense
will this work for clusters with 100+ or 200+ jobs? Does it paginate? This feels like an anti-feature, but I can see how it would be convenient. |
It will export 4 jobs at a time. If we choose to keep this feature I can test it on a large amount of jobs and see how it goes. |
|
3b30034
to
439c093
Compare
Exporting 30 jobs with name collisions:
I manually verified that each file has a unique jobId. |
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.
LGTM
A few special characters were added a documentation change in my recent PR: #3717 After merging the docs build failed because docusuarus could not parse the .md file properly. This PR escapes those characters properly.
This PR makes the following changes:
jobs export
command to teraslice-cliJobs
class using the provided jobIds, extracts the jobConfig for each job, and saves each config to the local file system../<job.name>.json
by default. If a file name already exists-N
will be appended to the file name.--outdir
flag will set a custom directory where job files are saved.all
will export all jobs. This can be combined with--status
to export all jobs with executions of a specific status.Ref: #3695