-
-
Notifications
You must be signed in to change notification settings - Fork 66
how to specify network access with example #381
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
base: main
Are you sure you want to change the base?
Changes from 3 commits
cefdd8a
b0dd765
d3b6994
5a9eca3
2f6dc78
d79bab1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -447,6 +447,51 @@ The reference runner and several other CWL implementations support running | |
those Docker format containers using the Singularity engine. Directly | ||
specifying a Singularity format container is not part of the CWL standards. | ||
|
||
## How do I specify when network access is required? | ||
|
||
In CWL v1.1 and above, you need to specify when network access is required by | ||
including the `NetworkAccess` requirement. | ||
If `networkAccess` is `true`the tool must be able to make | ||
outgoing connections to network resources. | ||
If `networkAccess` is `false` or not specified, is false or not | ||
specified, tools must not assume network access, except for localhost | ||
(the loopback device). | ||
|
||
Below is an example using `curl` where `networkAccess: true` which | ||
allows the page with the link in the yaml file to be downloaded and | ||
saves it in a `download.hmtl` file | ||
|
||
|
||
``` | ||
cwlVersion: v1.2 | ||
class: CommandLineTool | ||
|
||
requirements: | ||
NetworkAccess: | ||
networkAccess: true | ||
|
||
baseCommand: curl | ||
|
||
stdout: download.html | ||
|
||
inputs: | ||
url: | ||
type: string | ||
inputBinding: | ||
position: 1 | ||
|
||
outputs: | ||
out: | ||
type: File | ||
outputBinding: | ||
glob: download.html | ||
``` | ||
|
||
The input yaml file will be | ||
``` | ||
url: https://www.commonwl.org/v1.2/ | ||
``` | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we also need to document what happens when There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The flag doesn't block the network access; I ran the above code with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Correct. It's planned work for There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So can I say that when the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we must say what happens in both cases. We can probably use or adapt the text from the specification, where it explains it's an indicative flag, what implementations/users can expect, and the meaning of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alright, thanks! |
||
## Debug JavaScript Expressions | ||
|
||
You can use the <code>--js-console</code> option of <code>cwltool</code>, or you can try | ||
|
Uh oh!
There was an error while loading. Please reload this page.