Releases: broadinstitute/cromwell-tools
Releases · broadinstitute/cromwell-tools
v1.1.1
v1.1.0
- Improve the help messages of CLI and add shorthands for
submit
command. - Fix an issue that can stop local file from being normally processed.
- Fix the failing test by cleaning up the Dockerfile that relies on Oracle Java installer and move to use OpenJDK instead.
- Take the retry policy based on tenacity out from the cromwell-tools for clarity.
- Add token checker before making the header to avoid token expiration with OAuth.
- Fix a bug that prevents generating correct pagination parameters for POST
/query
endpoint. - Update the pull-request-template.
v1.0.1
- Fix a bug with the service account key that prevents users from using any authentication methods.
- Fix a bug with
/validate
command in CLI. - Fix a bug with
/health
endpoint in API. - Improve the output of the CLI commands.
- Update the documentation, quickstart Jupyter notebook, and docstrings.
- Update the authentication dependency from the deprecated
oauth2client
togoogle-auth
. - Allow no-auth with Cromwell.
v1.0.0
Changes:
- A breaking refactoring work on both the CLI and API.
- More sophisticated unit tests.
- Support both Python2 and Python3, having tests run on both versions.
- Updated ReadMe file and docstrings.
- For
/submit
endpoint, we support both path to the file and file contents as inputs now. - We have a quickstart example Jupyter Notebook now.
- Update requests to avoid security issues.
- Fix API calls in CLI.
- We have accessory tools with cromwell-tools, such as the workflow monitoring script.
- Other slight improvements and bug fixes.
Note: from this version we will start to publish this package on PyPI.
v0.5.0
v0.4.0
- Add on_hold parameter to start_workflow
- Add workflow validation capability
- Add Sphinx autodoc and readthedocs hook
- Bugfix: Allow workflows without labels to be executed
- Bugfix: Fix docker container build issues
v0.3.1
v0.3.0
Add option to use Cromwell-as-a-Service
Update the functions that make requests to Cromwell to send a bearer token generated from the CaaS key if the key is provided, otherwise use the username and password.