Cannot create remote service from within enterprise network proxy

[trailfox]

I am having issues trying to create an a127 RemoteProxy from within my companies network.

I am running on Ubuntu and have my http_proxy and https_proxy environment variables setup, along with npm config, so that I can deploy my a127 proxy up into Apigee Edge successfully. However, when I come to try and create a RemoteProxy for my a127 api so that I can setup Oauth, analytic policies etc I am finding that the create service command is failing.

From my debugging of the a127 code it appears that the Volos code is not using the http_proxy/https_proxy when trying to make requests up to Edge.

For example when the service create command requests the list of proxies in edge it gets those fine. But it is the Volos code which appears to not be using the http_proxy environment variable or the npm configuration when it is trying to get a list of the developer apps. When I use the Apigee online API management UI to get the list of developer apps it works fine. But debugging the volos code which is using the same API it fails.

Is there additional configuration that Volos is expecting to be setup for http_proxy/https_proxy?

[theganyo]

I'm sorry you've run into issues. The Volos runtime functionality does support the http_proxy/https_proxy env vars, but unfortunately the management functions (the part used by the a127 CLI to create the remote proxy) does not yet. The immediate solution would be to deploy the proxy using this: https://github.com/apigee-127/apigee-remote-proxy.

[trailfox]

thanks - that worked perfectly.

Any idea on when a127 CLI will get enhanced to support http_proxy/https_proxy env vars?

The next issue is regarding the creation of the Product, Developer and Developer App. Do these have to be manually created?

Also when I try to bind my a127 project to the remote proxy, the bind command cannot find the remote service I just created. I have verified that the remote service exists on Edge and that I get a 401 when I try and verify the remote service.

The help on the remote service setup assumes that you are using the a127 CLI commands.

[theganyo]

Sorry, I don't have anything firm at this point.

[trailfox]

Thanks for that.

I still have the following issues regarding the setup of the remote service behind the network proxy.

Using the a127 commands, a Product, Developer and Developer App are also created. However, using the apigee-remote-proxy command I am not seeing these being created in our edge account. Do these have to be manually created?

When I try to bind my a127 project to the remote proxy, the bind command cannot find the remote service I just created. I have verified that the remote service exists on Edge and that I get a 401 when I try and verify the remote service.

The help on the remote service setup assumes that you are using the a127 CLI commands.

Is there any help that explains this setup using the apigee-remote-proxy?