Changes for page Apply to environment
Last modified by Danniar Firdausy on 2024/09/17 12:39
From version 6.1
edited by Erik Bakker
on 2022/08/28 14:50
on 2022/08/28 14:50
Change comment:
There is no comment for this version
To version 11.1
edited by Danniar Firdausy
on 2024/06/25 08:47
on 2024/06/25 08:47
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -55,22 +55,25 @@ 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 58 -== 4.Assignment==58 +=== 3.1 Change log === 59 59 60 -There assignmentforthismicrolearning.60 +To inform you which changes will precisely be executed once you press "Apply to environment," we will show a pop-up listing all the pending **user** level changes that will be implemented once the user presses "Apply changes." 61 61 62 - == 5.Keytakeaways ==62 +[[image:Main.Images.Release Blog.WebHome@intermediate-emagiz-cloud-management-apply-to-environment-apply-to-environment-example.png]] 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 +{{warning}}Note the following: 65 +* Other settings could be applied which cannot be altered by the user. These changes are not shown to the user. 66 +* Indirect changes only take an effect after creating a new release and deploying this to the corresponding environment.{{/warning}} 66 66 67 -== 6.SuggestedAdditional Readings ==68 +== 4. Key takeaways == 68 68 69 -There are no suggested additional readings on this topic 70 +* Apply to environment actualizes all changes with an indirect effect 71 +* It gives you the option to change multiple things at once before applying the bulk change. This is to reduce downtime 72 +* It ensures that the eMagiz Cloud is only affected when a user want to affect it 70 70 71 -== 7. Silent demonstrationvideo==74 +== 5. Suggested Additional Readings == 72 72 73 -There isnodemonstrationvideoofthisfunctionality.)))76 +There are no suggested additional readings on this topic))) 74 74 75 75 ((({{toc/}}))){{/container}} 76 76 {{/container}}