Update 2.3.0 release notes (#218)
This commit is contained in:
Родитель
bebd22cc1a
Коммит
51b7dbfe50
|
@ -1,9 +1,9 @@
|
|||
# Welcome to Cromwell on Azure
|
||||
### Latest release
|
||||
* [Release 2.2.1](https://github.com/microsoft/CromwellOnAzure/releases/tag/2.2.1)<br/>
|
||||
[Release notes for version 2.2.1](docs/release-notes/2.2.1.md)
|
||||
* [Release 2.3.0](https://github.com/microsoft/CromwellOnAzure/releases/tag/2.3.0)<br/>
|
||||
[Release notes for version 2.3.0](docs/release-notes/2.3.0.md)
|
||||
|
||||
Check the "Update Instructions" section in the version 2.2.1 [release notes](docs/release-notes/2.2.1.md/#update-instructions) to learn how to update an existing Cromwell on Azure deployment to version 2.2.1. You can customize some parameters when updating. Please [see these customization instructions](docs/troubleshooting-guide.md/#Customize-your-Cromwell-on-Azure-deployment), specifically the "Used by update" and "Comment" columns in the table.<br/>
|
||||
Check the "Update Instructions" section in the version 2.3.0 [release notes](docs/release-notes/2.3.0.md/#update-instructions) to learn how to update an existing Cromwell on Azure deployment to version 2.3.0. You can customize some parameters when updating. Please [see these customization instructions](docs/troubleshooting-guide.md/#Customize-your-Cromwell-on-Azure-deployment), specifically the "Used by update" and "Comment" columns in the table.<br/>
|
||||
|
||||
#### Getting started
|
||||
* What is [Cromwell on Azure?](#Cromwell-on-Azure) <br/>
|
||||
|
|
|
@ -2,7 +2,8 @@
|
|||
## Bug fixes and enhancements
|
||||
|
||||
1. Disabled binary logging in MySQL to conserve disk space on the data disk ([#205](https://github.com/microsoft/CromwellOnAzure/issues/205))
|
||||
2. Fixed the logic that determines the top WorkflowId from TES Task properties. This only affects users who are directly querying CosmosDB and are using the WorkflowId field in a predicate ([#209](https://github.com/microsoft/CromwellOnAzure/issues/209)).
|
||||
2. Fixed the logic that determines the top WorkflowId from TES Task properties. This only affects users who are directly querying CosmosDB and are using the WorkflowId field in a predicate ([#209](https://github.com/microsoft/CromwellOnAzure/issues/209)).
|
||||
3. Occassionally the deployer would hang due to the VM not rebooting. Changed deployer reboot logic to use the OS-level command instead of the Azure RM command ([#217](https://github.com/microsoft/CromwellOnAzure/issues/217)).
|
||||
|
||||
## Update instructions
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче