Skip to Content
Last modified by Erik Bakker on 2024/09/03 07:58
From version 6.1
edited by Erik Bakker
on 2022/10/03 11:45
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2022/10/03 11:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -23,11 +23,11 @@
23 23  
24 24  The following consideration are valid when upgrading to a new Cloud template
25 25  
26 -1. Service affecting vs. non-service effecting
27 - Non-service affecting templates will not affect your current operation * flows will continue to function as usual. You can safely apply the cloud template. Service affecting means that that the machines will need to be stopped and started to make the cloud template operational. There is short window in which flows are not operational and there will be a delay in message delivery & processing. Messages is not lost.
26 +* Service affecting vs. non-service effecting
27 +** Non-service affecting templates will not affect your current operation * flows will continue to function as usual. You can safely apply the cloud template. Service affecting means that that the machines will need to be stopped and started to make the cloud template operational. There is short window in which flows are not operational and there will be a delay in message delivery & processing. Messages is not lost.
28 28  
29 -2. Other changes pending for an AWS update
30 - The apply to environment button will apply all the changes that are made in Design architecture and Deploy architecture. These can be things such as
29 +* Other changes pending for an AWS update
30 +** The apply to environment button will apply all the changes that are made in Design architecture and Deploy architecture. These can be things such as
31 31  
32 32  * Memory changes
33 33  * Runtimes removed