Feat: release-v2.11.0 - Adds save_logs
and removes spot
options from job
command
#166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR does two things:
cloudos job run
command will save process logs. There is a new flag parameter:--do-not-save-logs
to allow not saving logs (previous default).--spot
option, which is no longer available in CloudOS. However, to maintain backwards compatibility, if the user uses--spot
, a message will be displayed informing that the parameter is no longer valid.Jira
https://lifebit.atlassian.net/browse/LIF-290
https://lifebit.atlassian.net/browse/LIF-293
Changes
--do-not-save-logs
parameters for all the job run commands (cloudos job run
andcloudos job run-curated-examples
).--spot
option from job run commands.--do-not-save-logs
to the message when runninghpc
executor, as it will be ignored.Tests
Using docker image:
Global variables:
Running
cloudos job run
(default)Running
cloudos job run-curated-examples
(default)Running
cloudos job run --execution-platform hpc
Running
cloudos job run
not saving logs (using--do-not-save-logs
flag)Running
cloudos job run
using--spot
option