Skip to Content
Last modified by Erik Bakker on 2023/08/04 13:41
From version 1.2
edited by eMagiz
on 2022/06/09 11:54
Change comment: Update document after refactoring.
To version 2.1
edited by eMagiz
on 2022/06/09 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -intermediate-emagiz-cloud-management-apply-to-environment
1 +Apply to environment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.eMagiz
Content
... ... @@ -1,16 +1,11 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
4 4  
5 -<div class="doc">
6 6  
7 -
8 -
9 -= Apply to environment =
10 -
11 11  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.
12 12  
13 -Should you have any questions, please contact academy@emagiz.com.
8 +Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14 14  
15 15  * Last update: July 21th, 2021
16 16  * Required reading time: 5 minutes
... ... @@ -65,7 +65,6 @@
65 65  
66 66  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.
67 67  
68 -===== Practice =====
69 69  
70 70  == 4. Assignment ==
71 71  
... ... @@ -86,9 +86,7 @@
86 86  
87 87  There is no demonstration video of this functionality.
88 88  
89 -</div>
83 +)))
90 90  
91 -</div>
92 -</div>
93 -
94 -{{/html}}
85 +((({{toc/}}))){{/container}}
86 +{{/container}}