Wiki source code of 212 - Failover Fiesta
Version 185.1 by Carlijn Kokkeler on 2024/01/15 14:46
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
184.1 | 1 | In the last sprint cycle, we focused on .... |
| |
1.1 | 2 | |
| |
185.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. |
| |
35.1 | 4 | |
| |
155.1 | 5 | =====New features===== |
| |
150.1 | 6 | |
| |
179.1 | 7 | * Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. |
| |
174.1 | 8 | * Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. |
| |
156.1 | 9 | |
| |
109.1 | 10 | =====Minor changes===== |
| |
93.1 | 11 | |
| |
174.1 | 12 | * Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. |
| |
175.1 | 13 | * Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. |
| |
183.1 | 14 | * Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. |
| |
181.1 | 15 | * Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917) |
| |
175.1 | 16 | * Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. |
| |
173.1 | 17 | * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. |
| |
93.1 | 18 | |
| |
159.1 | 19 | ====Bug fixes==== |
| |
155.1 | 20 | |
| |
174.1 | 21 | * Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. |
| |
182.1 | 22 | * Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. |
| |
177.1 | 23 | * Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. |
| |
180.1 | 24 | * Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container. |
| |
181.1 | 25 | * Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108) |
| |
158.1 | 26 | |
| |
101.1 | 27 |