fcli * action
: Add support for running ScanCentral and possibly other commands
#548
Labels
effort:medium
Medium effort needed to implement/fix
fcli-actions
feature
A feature that's on the roadmap or in development
prio:high
High priority; important new feature or bug fix
If we ever want to implement pipeline-style actions, we'd need to allow actions to run the
scancentral package
command, and possibly any other commands. We could either:package:
instruction that explicitly invokes thescancentral package
command with any given argumentsscancentral:
instruction that allows for invoking anyscancentral
commandrun:
instruction for running arbitrary commandsOf course, we could also provide multiple of these options, like both a
package:
andrun:
instruction.With options 1 and 2, the actions framework could potentially automatically download & install ScanCentral Client if it's not available yet, and potentially even remove this once the action terminates, or potentially these instructions could use an embedded ScanCentral Client. Of course, ideally, at some point packaging functionality should be incorporated into fcli.
With option 3, ScanCentral Client would already need to be installed, either manually by the user before running the action, or by the action itself by running
fcli tool sc-client install
before therun:
step.The text was updated successfully, but these errors were encountered: