Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 175.1
edited by Carlijn Kokkeler
on 2023/12/21 16:27
on 2023/12/21 16:27
Change comment:
There is no comment for this version
To version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
on 2023/12/21 16:12
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,25 +4,16 @@ 4 4 5 5 =====New features===== 6 6 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 in an overview. 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. 9 9 8 + 10 10 =====Minor changes===== 11 11 12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 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. 14 -* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. 16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 17 * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 18 18 13 + 14 + 19 19 ====Bug fixes==== 20 20 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. 22 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container. 23 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. 24 -* Deploy - Cloud templates: An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 25 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 26 26 27 27 28 28