Changes for page 213 - Joyful Journeys

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-211 - Log Luminary
	1	+209 - Deployment Delights

Content

...	...	@@ -3,74 +3,45 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	6	+**Hi there, eMagiz developers!** We have...
7	7
8		-== **TBD** ==
	8	+== **Release Maintenance** ==
9	9
10	10
11	11
12		-== **Feedback Items** ==
13	13
14		-//__Runtime overview__//
15		-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.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
	14	+== **Feedback Items** ==
18	18
19		-//__Missing properties overview__//
20		-The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
	16	+//__Harbor port change__//
	17	+The port for which you need to register has been changed ...?
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
	19	+//__Container version overview__//
	20	+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.
23	23
24		-//__Breaking changes pop-up__//
25		-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'.
	22	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
26	26
27		-[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
	24	+//__Unchanged containers__//
	25	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
28	28
29		-//__External recipients emailaddress__//
30		-The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
	27	+//__Rebuilding of images__//
	28	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31	31
32		-//__Broker queue metrics dashboards__//
33		-It is now possible to select the MQTT broker in the queue metrics dashboards.
34	34
35		-//__Runtime image version__//
36		-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.
37		-
38		-//__Runtime restart or redeploy overview__//
39		-Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
40		-
41		-[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
42		-
43	43	== **Bug Fixes** ==
44	44
45		-//__Message throughput__//
46		-The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
	33	+//__Runtime metrics processing__//
	34	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
47	47
48		-//__Deployment execution error message__//
49		-In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
	36	+//__Deployment plan__//
	37	+We solved a bug where a deployment step in the deployment plan could get stuck randomly.
50	50
51		-//__Cloud template upgrade unjust rollback__//
52		-An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
53		-
54		-//__Missing log entries__//
55		-We improved crash handling so that log messages clearly show when and why a container failed to start.
56		-
57		-//__Runtime logging__//
58		-We fixed a bug where no new log messages were showing up, even though they were produced by the container.
59		-
60		-
61		-
62		-
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
68		-* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
69		-* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
70		-* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
71		-* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
	43	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
72	72
73		-
74	74	== **Key takeaways** ==
75	75
76	76	Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: