-
Notifications
You must be signed in to change notification settings - Fork 94
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: default workflow from source dir? #4929
Comments
This has been discussed, the current behaviour is as designed, it might be in a proposal somewhere? Because installation is not a 1:1 mapping, it is not really possible to do this without things getting confusing / dangerous when multiple installations are involved. $ cd ~/cylc-src/x
$ cylc install --workflow-name foo
$ cylc install --workflow-name bar
$ cylc play # eh? what do you want me to do?
$ cylc ~/cylc-src/y
$ cylc install
$ sleep 1d # come back to things later
$ cylc install -n foo
$ cylc play # opps, I've messed with the previous installation The mapping between an installed workflow and it's source are contained in the |
We have also discussed inferring the workflow from the run rather than source directory (which is much easier). As it happens, |
That's why I said, default to [the default latest install] That would be reasonable wouldn't it? i.e. if you do not specify a workflow ID and you are in a source directory, default to the default-form latest-run ID if it exists. This would be quite an ease-of-use convenience for those using the default install locations. (Which ought to be most of us, most of the time). |
But, to go further than that, perhaps we could put a latest-install symlink in source directories? |
This would simply fail, with Unless of course
This would attempt to play However, a latest-install symlink in the source directory might be even better? |
#3896 will make this much easier (e.g. |
@hjoliver - Do you think that we will have sig user demand for this feature? And if we do will it be for playing the latest (runN) install, or for playing "the install I meant to play" (no matter how hard that might be to deduce). If we are being ruthless about release dates I think that it's a post 8.0 feature because it won't break anyone's working practice if we add it later. |
(If we implement |
User feature request:
If I'm in a source directory
~/cylc-src/foo
(say),cylc install
defaults to installing a new copy offoo
asfoo/runN
.If I'm still in
~/cylc-src/foo
couldcylc play
andcylc stop
etc. default tofoo/runN
too, if it exists?This would be convenient during development, in the source directory, which typically involves a lot of repetition of
cylc install
thencylc play my-long-workfow-id
andcylc stop my-long-workflow-id
.Trying to recall why we don't do this:
cylc trigger //1/model
?)The text was updated successfully, but these errors were encountered: