Models for Future Structured Tool State Work

[jmchilton]

"Meta" models describing tool inputs. The downstream work already includes client side validation of tool request and near instant async tool form submission and background job creation based on these models (#17393). Future work will include JSON schema definitions for the internal tool state for the execution of a single job, tool request tool state JSON schema that describes map/reduce operations available in the API that transcend multiple jobs, cleaner and more robust CWL implementations.

This part is the models and test validation framework that verify implementations as well the exposure of these models via the Tool Shed 2.0 API - both as the pydantic meta model description and as the JSON schema for the future tool request API. Future ToolShed 2.0 APIs will include JSON schemas for workflow definitions and tool test cases.

More information on the tool state project can be found at https://docs.google.com/document/d/1HQOLpLN54CjrB-wbD463XqzvUm-dNB8vTXUFBExh_2o/edit?usp=sharing.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jmchilton]

I think tool section tags aren't implemented in the models - but given we're not touching Galaxy internals I think they can just get filled in in subsequent PRs adding more test cases and such.

[jmchilton]

The tool state stuff in here is solid - but I've made a bunch of progress on I think a better tool shed 2.0 tool endpoint. I'm going to close this out and stabilize a PR I feel has a rich shed endpoint and a more future facing approach to caching.