Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 99.1
edited by Erik Bakker
on 2023/08/01 14:57
Change comment: There is no comment for this version
To version 167.1
edited by Carlijn Kokkeler
on 2023/12/04 15:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,36 +1,24 @@
1 -In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
1 +In the last sprint cycle, we focused on improving several aspects related to the deployments. It is now possible to see an overview of container versions, and containers will not be deployed and restarted when no changes have been made. Moreover, several bug fixes have been done, relating to the Flow Designer, the Deploy phase, and alerting.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.202 - New Equilibrium.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 -* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 -* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
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.
11 11  
12 12  =====Minor changes=====
13 13  
14 -* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 -* Deploy - Releases: The infographic has been updated.
16 -* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 -* Deploy - Property release: Names of properties can be created/removed/edited.
18 -* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 -* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#996)
20 -* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 -* Infrastructure: Tightened security policies for a more secure infrastructure.
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.
22 22  
23 23  ====Bug fixes====
24 24  
25 -* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 -* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 -* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 -* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 -* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 -* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 -* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 -* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 -* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 -* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 -* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
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.
36 36  
24 +