You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In APIM 410, an inconsistent behavior was observed where the revision deployment call(using publisher REST APIs) is getting passed without any issue even with the wrong vhost parameter.
Steps to Reproduce
create a new gateway environment us-region with us.wso2.com and foods.com vhosts.
Then we use Publisher REST API to deploy a new revision with the below payload.
[
{
"revisionUuid": "194d5ba6-7d0c-4276-9089-d5e99077e167",
"name": "us-region",
"vhost": "ws.wso2.com",
"displayOnDevportal": true
}
]
As you can see in the payload, we are passing a wrong vhost(ws.wso2.com) with the correct gateway name.
The API call is getting invoked without any issue and the new revision is getting deployed into the gateway with the wrong vhost.
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Description
In APIM 410, an inconsistent behavior was observed where the revision deployment call(using publisher REST APIs) is getting passed without any issue even with the wrong vhost parameter.
Steps to Reproduce
create a new gateway environment us-region with us.wso2.com and foods.com vhosts.
Then we use Publisher REST API to deploy a new revision with the below payload.
[
{
"revisionUuid": "194d5ba6-7d0c-4276-9089-d5e99077e167",
"name": "us-region",
"vhost": "ws.wso2.com",
"displayOnDevportal": true
}
]
As you can see in the payload, we are passing a wrong vhost(ws.wso2.com) with the correct gateway name.
The API call is getting invoked without any issue and the new revision is getting deployed into the gateway with the wrong vhost.
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: