This repository has been archived by the owner on Mar 13, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 64
Require invoker name for 'riff create' and 'riff init' and clarify usage in help #502
Comments
If we go through with this, this is a matter of completely removing the This would simplify the codebase for sure. I am in favor of it, as I agree users know they want to create a "java" function for example, when they have a |
see also #517 |
ericbottard
added a commit
to ericbottard/riff
that referenced
this issue
Apr 5, 2018
…tead of "command". Fixes projectriff#502
#518 only addressed the doc part of this issue |
scothis
added a commit
to scothis/riff
that referenced
this issue
Apr 6, 2018
riff will no longer attempt to resolve an invoker based on the files in the current directory. The previous resolution could change behavior as` new invokers are installed in the cluster or files change on disk. Fixes projectriff#502
scothis
added a commit
that referenced
this issue
Apr 6, 2018
riff will no longer attempt to resolve an invoker based on the files in the current directory. The previous resolution could change behavior as` new invokers are installed in the cluster or files change on disk. Fixes #502
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The CLI UX would be simpler if an invoker parameter were required for all
riff create <invoker>
andriff init <invoker>
commands. If no invoker is specified, display a usage error and the list of registered invokers.this is a followup to #448
Auto-detecting invokers from file extensions introduces non-determinism. E.g. adding new invokers could break old workflows by stealing the extension. This is true even when pointing to a source file with --artifact.
The current command-invoker already makes it necessary always to disambiguate, because it matches *.
It's often eaiser to specify an invoker than point to an "artifact" file (invoker names are short).
with this approach we could even auto-generate the source file when there are no files at all in the directory. E.g.
riff create node --stream
The text was updated successfully, but these errors were encountered: