search

wso2 / product-apim

Welcome to the WSO2 API Manager source code! For info on working with the WSO2 API Manager repository and contributing code, click the link below.
http://wso2.github.io/
Apache License 2.0
845 stars 785 forks source link

Issue with invoking the Api after an Gateway environment is updated #6008

Closed shananjana closed 5 years ago

shananjana commented 5 years ago

We have initialized different Gateway Environments by using deployment.toml

Screenshot from 2019-10-09 14-58-11

when we Publish the API by using one gateway environment that we have deployed, we can execute the API properly in the DevPortal.

If we change the gateway environment of that published API, in the first instance it shows that the API is updated successfully. Although it shows like that, we cant invoke the API with the correct token even. The updated gateway environment is visible on the overview page of the dev portal. But although we have the correct key, we won't be able to invoke the API.

Screenshot from 2019-09-30 15-20-06

npamudika commented 5 years ago

Republishing the API will solve the issue. We need to check and fix the logic behind save operation to publish to newly added gateway environments.

Krishanx92 commented 5 years ago

This issue cannot reproduce in APIM-3.0.0-beta, hence resolve.