Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
Change comment: There is no comment for this version
To version 177.1
edited by Carlijn Kokkeler
on 2023/12/21 16:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,16 +4,24 @@
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.
7 7  
8 -
9 9  =====Minor changes=====
10 10  
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.
11 11  * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
12 12  
13 -
14 -
15 15  ====Bug fixes====
16 16  
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 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal.
17 17  
18 18  
19 -