Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 166.1
edited by Carlijn Kokkeler
on 2023/12/04 15:52
Change comment: There is no comment for this version
To version 56.1
edited by Erik Bakker
on 2023/03/03 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +193 - Fan Out
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,24 +1,24 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
1 +The release introduces REST/XML as an option for your gateway operations and new features for our 3rd generation runtime, a new runtime image, and new cloud templates. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.193 - Fan Out.WebHome||target= "blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
7 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V130.WebHome||target="blank"]].
8 +* Design - Settings: We added XML support to API Management. To enable this feature, change the 'Default message format' in the Design settings section. You can change individual operations by changing the message format of your gateway message. Migrating existing operations requires a reset of the exit flow and a change in the catalog in Design. For more information, see the release blog post. (#815)
9 +* Deploy - Releases: New release properties pop-up that shows all properties in your release, grouped by containers that they are assigned to. This pop-up can be accessed by pressing the wrench-shaped icon, which becomes available once a release is set as active.
8 8  
9 9  =====Minor changes=====
10 10  
11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
13 +* Design - API Gateway: OData API type exclusively selectable for system admin. (#816)
14 +* Design - API Catalog: When you change a path in the Design phase, your HTTP inbound gateways that use the changed path will also be updated in Create phase if you have edit rights. (#524)
15 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
16 +* Manage - Error messages: Message history is sorted by timestamp descending.
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 -
24 -
20 +* Create - Message Definition: Attribute can be declared as JSON array in API Gateway and Event Streaming. (#908)
21 +* Create - Migration: We fixed a third-generation migration issue where the legacy error handling flow components were not removed from the asynchronous routing flow.
22 +* Create - Flow designer: when migrating a container’s flows from gen2 to gen 3, “global wire tap” components and their relevant components will be removed.
23 +* Deploy - Release: We fixed an issue that caused images not to be built in specific situations when running in the new runtime generation runtime.
24 +* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. (#797)