Skip to Content

Changes for page Apply to environment

Last modified by Danniar Firdausy on 2024/09/17 12:39
From version 2.1
edited by eMagiz
on 2022/06/09 11:56
Change comment: There is no comment for this version
To version 3.1
edited by Erik Bakker
on 2022/08/28 14:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Content
... ... @@ -7,9 +7,6 @@
7 7  
8 8  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
9 9  
10 -* Last update: July 21th, 2021
11 -* Required reading time: 5 minutes
12 -
13 13  == 1. Prerequisites ==
14 14  
15 15  * Basic knowledge of the eMagiz platform
... ... @@ -24,8 +24,6 @@
24 24  * It gives you the option to change multiple things at once before applying the bulk change. This is to reduce downtime
25 25  * It ensures that the eMagiz Cloud is only affected when a user want to affect it
26 26  
27 -
28 -
29 29  == 3. Apply to environment ==
30 30  
31 31  In this microlearning, we will focus on the "apply to environment" action. As we saw in previous microlearnings and will see in microlearnings to come with regards to cloud management is that some actions in Deploy Architecture have a direct effect (i.e. Slot Wakeup, Restart Runtime, Reset Runtime, etc.) and others have an indirect effect (i.e. Add Route, Add Certificate, Remove Runtime, etc.). For the actions that have an indirect effect on the eMagiz Cloud you need the "apply to environment" functionality to actualize the changes on the eMagiz Cloud level.
... ... @@ -60,7 +60,6 @@
60 60  
61 61  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.
62 62  
63 -
64 64  == 4. Assignment ==
65 65  
66 66  There is no assignment for this microlearning.
... ... @@ -70,8 +70,6 @@
70 70  * By restarting the runtime, you restart all flows (including infra) of the runtime you have selected
71 71   * Flows return in original state
72 72  
73 -
74 -
75 75  == 6. Suggested Additional Readings ==
76 76  
77 77  There are no suggested additional readings on this topic
... ... @@ -78,9 +78,7 @@
78 78  
79 79  == 7. Silent demonstration video ==
80 80  
81 -There is no demonstration video of this functionality.
73 +There is no demonstration video of this functionality.)))
82 82  
83 -)))
84 -
85 85  ((({{toc/}}))){{/container}}
86 86  {{/container}}