Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 279.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
Change comment: There is no comment for this version
To version 268.1
edited by Carlijn Kokkeler
on 2023/12/04 13:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,39 +13,13 @@
13 13  
14 14  == **Feedback Items** ==
15 15  
16 -//__Container version overview__//
17 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
16 +//__Unused properties overview__//
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
20 20  
21 -//__Unchanged containers__//
22 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 -
24 -//__Rebuilding of images__//
25 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26 -
27 -
28 28  == **Bug Fixes** ==
29 29  
30 -//__Runtime metrics processing__//
31 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
32 32  
33 -//__Deployment plan__//
34 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 35  
36 -//__Store message merging__//
37 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
38 -
39 -//__View all store items__//
40 -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.
41 -
42 -//__Out of memory behavior__//
43 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 -
45 -//__Max fetch size__//
46 -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.
47 -
48 -
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: