No proxy deployed but traffic is still routing

[#1]

Hello all,

We have undeployed everything from our organisation's environment and tested this by using the following REST API: -

https://api.enterprise.apigee.com/v1/organizations/the_org/apis/the_name/deployments

We receive the following JSON back:

{ "environment": [], "name": "the_name", "organization": "the_org" }

When we hit our apigee endpoint, we seem to be still routing to the target.

Why is this the case? with no proxy deployed, there should be no routes to the target?

[sidd-harth]

Hi @Christopher Webb , the JSON response confirms that your api proxy exists but is not deployed in any env.

{ "environment": [], "name": "the_name", "organization": "the_org" }

Once undeployed, the apigee endpoint should give "Unable to identify proxy for host"

Which Apigee instance are you working on? Free-Cloud/On-prem?

[#3]

It is on an On-Prem Apigee instance; I expect that we should be getting "Unable to identify proxy for host", however we are simply seeing the target, as if the proxy were deployed.

[shrinivaskulkar]

Did you ever get an answer on this issue? We just upgraded our on-prem version to 4.18.05 and are seeing the same issue.