Changes for page Updating your API Gateway Operations
Last modified by Danniar Firdausy on 2024/09/30 17:12
From version 35.76
edited by Danniar Firdausy
on 2024/09/30 12:34
on 2024/09/30 12:34
Change comment:
There is no comment for this version
To version 35.78
edited by Danniar Firdausy
on 2024/09/30 12:39
on 2024/09/30 12:39
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -87,11 +87,15 @@ 87 87 88 88 ==== 3.3.5 Edit Responses ==== 89 89 90 - Lastly, the "Responses" tab of the API Catalog page also allows you to specify the response description and example response (along with its "Media type") for a specific HTTP status code.The screenshot below shows what are listed in the "Responses" tab is reflected in the Swagger UI.90 +The "Responses" tab of the API Catalog page also allows you to specify the response description and example response (along with its "Media type") for a specific HTTP status code. 91 91 92 +[[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--edit-responses.png]] 93 + 94 +The screenshot below shows what are listed in the "Responses" tab is reflected in the Swagger UI. 95 + 92 92 [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--responses-description.png]] 93 93 94 - 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.98 +Lastly, 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. 95 95 96 96 {{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}} 97 97