-
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
cli: infer run number where possible #3895
Milestone
Comments
Just to emphasise the last point (more of a note to self really): named runs (with |
Will attempt after #4180 |
Bumped the centralisation of workflow argument parsing into a separate issue to make this one a little clearer - #4230 |
7 tasks
MetRonnie
changed the title
cli: infer run name where possible
cli: infer run number where possible
Jun 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempt after
#3889, #4230The default behaviour of
cylc install
will be to install workflows into an automatically named run (i.e.run<N>
).This means that the CLI will become a little cumbersome e.g.
To combat this we should make the relevant Cylc subcommands (those with a REG argument) run-dir aware. That is to say that if the REG provided is not a workflow (denoted by the presence of a
.service
directory) but does contain automatically named runs (denoted by the presence of arunN
symlink), then default to whatever runrunN
is pointing at.This change returns the CLI REG argument to the way it was before for most cases whilst providing the ability to control named runs individually where required.
The text was updated successfully, but these errors were encountered: