We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have not yet found an example where a step produces usable non-file target. We have
executable
$PATH
R_Library
Py_Module
system_resources
sos_step
sos_variable
shared
output: sos_variable('var')
So the concept of output: non-file-target seems to be useless. However, in the future we might have
output: non-file-target
named_pipe()
s3_bucket
socket
These are possible but at this point I cannot imagine how they should work.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have not yet found an example where a step produces usable non-file target. We have
executable
, possible, but even if we can generate an executable in a step, it is not necessarily in$PATH
so it still may not exist to sos.R_Library
andPy_Module
: Possible but cannot imagine building a module from a SoS step. Besides, these targets can try to install themselves.system_resources
: no way to change system resource to make it available.sos_step
: no need to generatesos_variable
: useshared
to generate, unless we want to change the syntax tooutput: sos_variable('var')
, which might actually work.So the concept of
output: non-file-target
seems to be useless. However, in the future we might havenamed_pipe()
which creates a pipe that other steps can read,s3_bucket
to produce a S3 bucket from AWS?socket
to pass something?These are possible but at this point I cannot imagine how they should work.
The text was updated successfully, but these errors were encountered: