Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 15:40
From version 7.1
edited by Erik Bakker
on 2022/08/25 12:08
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/08/25 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -56,15 +56,16 @@
56 56  In the previous segment, we talked about the impact of changing things in Design Architecture. In this segment, we will look at some scenarios in which the Design Architecture view can differ from the Deploy Architecture view. There are three main reasons why both of them differ:
57 57  
58 58  * This is the first time you open Deploy Architecture
59 - * This means you need to spin up your cloud infrastructure for the first time
59 +* This means you need to spin up your cloud infrastructure for the first time
60 60  * There is no flow related to the runtime embedded in the release
61 - * Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release
62 - * Note that this can differ per environment
61 +* Runtimes won't show up in Deploy Architecture when no flow should be deployed on them within the currently active release
63 63  * The runtime is excluded in Design Architecture
64 - * With this functionality, you explicitly mention that a certain runtime should not be deployed
63 +* With this functionality, you explicitly mention that a certain runtime should not be deployed
65 65  
66 66  Knowing this should make you better equipped to handle 'unexpected' situations you occur while implementing your data model with the help of the eMagiz platform.
67 67  
67 +{{info}}Note that the reason why you see a specific runtime can differ per environment.{{/info}}
68 +
68 68  == 4. Assignment ==
69 69  
70 70  Read up on the release notes of the various platform components and determine for the projects in which you operate what the status is of your eMagiz solution on the eMagiz platform.