![]() ~$ curl -s $TRS_ID/versions/$TRS_VERSION/WDL/descriptor | jq '.checksum' ~$ TRS_ID=%23workflow%%2Fdockstore-testing%2Fdockstore-workflow-md5sum-unified%2Fwdl This is done by requesting the PLAIN_WDL, PLAIN_CWL, PLAIN_NFL, or PLAIN_GALAXY descriptor type and piping the output to shasum. The id parameter used in the endpoints above can be found on an entry’s public page underneath the Info tab, look for the bolded words TRS.Īfter gathering the checksum using the above method you can verify a descriptor’s checksum using the shasum terminal application. More specifically, the endpoints that contain checksums for files are as follows: You must publish your entry in order to access the information via our TRS V2 endpoints. File Descriptor Checksum Support ĭockstore returns a SHA-256 checksum for every container, descriptor, and test parameter file included in a Keep reading to learn what is supported and how to retrieve the checksum information. Currently, checksums are not accessible through the UI, but can be fetched by using various TRSĮndpoints. To help developers who want to distribute or run immutable copies of tools and workflows, Dockstore (1.9+) can provide checksums for files and Docker Launching workflows using WES and the Dockstore CLI.Detailed Comparison of Tools and Workflows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |