Skip to Content
Last modified by Danniar Firdausy on 2024/09/30 17:12
From version 35.7
edited by Danniar Firdausy
on 2024/09/18 13:31
Change comment: There is no comment for this version
To version 35.9
edited by Danniar Firdausy
on 2024/09/27 13:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,6 +47,9 @@
47 47  
48 48  === 3.3 Updating the Swagger UI ===
49 49  
50 +Next to that, you can also update the Swagger UI of your API Gateway solution, so that it better informs your (external) parties to see the specifications of your API Gateway. As you have learned from the previous microlearning of the [[Swagger UI>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-swagger-ui||target="blank"]],
51 +
52 +
50 50  As is the case with all new versions in Create, the changes will only be effective when you deploy your solution via the eMagiz Deploy phase.
51 51  
52 52  {{info}}To ensure that the changes to your Swagger file generated by eMagiz are shown to the end-user, the latest version of the API Gateway runtime infra flow needs to be included in the release and deployed to the correct environment.{{/info}}
... ... @@ -53,13 +53,6 @@
53 53  
54 54  == 4. Key takeaways ==
55 55  
56 -* Updating can happen from Design
57 -* Updating can happen from Create
58 -* Both situations have a different impact
59 -* Adding a new operation to an existing solution does not involve a reset
60 -* Updating from Create does not involve a reset
61 -* Updating from Design does not involve a reset
62 -
63 63  * Updates to your API Gateway can be made either during the Design phase or the Create phase, each with distinct impacts.
64 64  * Changes made in the Design phase affect the configuration of the entry gate and may necessitate updates to both entry and exit gates, depending on the nature of the changes.
65 65  * Changes during the Create phase typically involve modifications to gateway messages, with changes reflected automatically in the Swagger definition and a version bump of the infra flow.
... ... @@ -66,7 +66,6 @@
66 66  * Adding new operations or updating from either Design or Create does not require a reset of the existing solution.
67 67  * Ensure that updates are included in the deployment phase to reflect the latest changes in the Swagger file and runtime infra flow.
68 68  
69 -
70 70  == 5. Suggested Additional Readings ==
71 71  
72 72  If you are interested in this topic and want more information, please read the help text provided by eMagiz and see the following link: