Add a `--no-cache` flag for `agc workflow run`
Description
A flag that will indicate that the run should not use any cached results.
Use Case
Provides a universal mechanism to disable call caching for a specific run. Each engine has different syntax for this so a universal flag is desirable rather than having to remember if it is a something to put in an options.json or as a command line variable.
Proposed Solution
AGC will parse the flag and send to the WES endpoint which will construct the appropriate command for it's engine. User will be warned if the engine doesn't support call caching or get an error if it cannot be disabled for some reason.
Other information
Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.
Commenting to keep this open.