30
30 Release Notes
Breaking changes
- The
customLabels
form field for workflow submission has been renamed tolabels
.
Other changes
-
New Cromwell documentation
Our documentation has moved from our README to a new website: Cromwell Documentation. There are new Tutorials and much of the documentation has been re-written. The source files are in the /docs directory. -
API
- Cromwell now supports input files in the yaml format (JSON format is still supported).
- Added a GET version for the
labels
endpoint which will return current labels for a workflow.
-
Database
You have the option of storing the metadata in a separate SQL database than the database containing the internal engine data. When switching connection information for an existing database containing historical data, the tables should be manually replicated from one database instance to another using the tools appropriate for your specific database types. Cromwell will not move any existing data automatically. This feature should be considered experimental and likely to change in the future. See the Database Documentation or thedatabase
section in cromwell.examples.conf for more information. -
StatsD
Added initial support for StatsD instrumentation. See the Instrumentation Documentation for details on how to use it. -
User Service Account auth mode for Google
Added a new authentication mode for Google Cloud Platform which will allow a user to supply the JSON key file in their workflow options to allow for per-workflow authentication via service account. This is analogous to the previously existing refresh token authentication scheme. As with the refresh token scheme it is encouraged that the user_service_account_json workflow option field is added to the encrypted-fields list in the configuration. -
Bugfixes
Abort of Dockerized tasks on the Local backend should now work as expected. Cromwell usesdocker kill
to kill the Docker container.