Changes for page Apply to environment

Summary

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

Details

Page properties

Content

...	...	@@ -51,7 +51,7 @@
51	51	| Clean Store |
52	52	| Upgrade Cloud Slot* |
53	53
54		-{{info}}* Note that the upgrade of the cloud slot can be planned for a later moment in time.{{/info}}
	54	+{{info}}~* Note that the upgrade of the cloud slot can be planned for a later moment in time.{{/info}}
55	55
56	56	So, in short, when you execute one (or more) actions on Deploy Architecture that have an indirect effect, you need to press Apply to Environment to actualize the changes within the eMagiz Cloud. Note that each move, whether it is direct or indirect, will cause a reaction and subsequent change within the eMagiz Cloud. So be cautious about changing things too many times over. Make sure you are especially careful when using custom folders on runtime level, as they could be deleted and recreated in cases where the machine is recreated. To safeguard yourself against this, place the folder either inside the data folder or directly on efs. Furthermore, we advise stopping the processes that have such custom folders before executing the change. This is especially relevant in the Production environment.
57	57
...	...	@@ -61,8 +61,9 @@
61	61
62	62	== 5. Key takeaways ==
63	63
64		-* By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
65		- * Flows return in original state
	64	+* Apply to environment actualizes all changes with an indirect effect
	65	+* It gives you the option to change multiple things at once before applying the bulk change. This is to reduce downtime
	66	+* It ensures that the eMagiz Cloud is only affected when a user want to affect it
66	66
67	67	== 6. Suggested Additional Readings ==
68	68