Apigee Network call error

[srinivasmurari]

hi,
when we tried to deploy API proxies using the cicd pipeline we are not able to deploy and got Apigee Network to call error and connection timed out issue,we need to connect via proxy to do any deployments from cicd server we had added proxy in our seetings.xml file and using 2.3.0 maven deploy plugin.

we have tested sample management APIs using bearer token we can make post & get from the same cicd server, but using the plugin we are getting the below-attached issue
deploy command used
mvn clean install -phybrid-apiproxy -Dorg=orgname -Denv=envname -Dbearer=token

[ssvaidyanathan]

@srinivasmurari - Looks like the machine where this is running is not able to access apigee.googleapis.com
Can you please confirm the machine can access? Do you need to pass any proxy settings?

[srinivasmurari]

we can access apigee.googleapis.com from the same machine (we are tested a management API from the machine we have created a target server)
Yes, we have proxy settings, we have added a proxy in our settings.xml, and we are using the 2.3.0 maven plugin.

[ssvaidyanathan]

Can you share the contents of your settings.xml? Hope you are using "https". Thats the only supported protocol.

If the proxy is setup correctly, you should see something like this in your console output. Can you check your console to see if anything similar is logged?

By the way the latest version is v2.4.3

[srinivasmurari]

<settings> <localRepository>/root/.m2/repository/</localRepository> <pluginGroups> <pluginGroup>org.apache.maven.plugins</pluginGroup> <pluginGroup>org.codehaus.mojo</pluginGroup> </pluginGroups> <interactiveMode>false</interactiveMode> <offline>false</offline> <mirrors> <mirror> <id>nexus</id> <mirrorOf>*</mirrorOf> <url>file:///root/.m2/repository</url> </mirror> </mirrors> <servers> <server> <id>snapshot</id> <url></url> </server> <server> <id>release</id> <url></url> </server> </servers> <activeProfiles> <!--make the profile active all the time --> <activeProfile>nexus</activeProfile> </activeProfiles> <proxies> <proxy> <id>https_proxy</id> <active>true</active> <protocol>https</protocol> <host>proxyip</host> <port>proxyport</port> <nonProxyHosts></nonProxyHosts> </proxy> </proxies> </settings>
setting.xml

Yes we are using https proxy in setting.xml.
we can see the proxy as per the link above in our console output.

[srinivasmurari]

Hi @ssvaidyanathan ,

Kindly do the needful, currently, we are blocked at this point. if you need more info let us know.

[ssvaidyanathan]

@srinivasmurari - I am assuming you have actual proxy host and port in your settings.xml and thats what the log is showing?

If thats true, thats the extent I can help you with. I know other customers using this plugin with the proxy settings and its working for them without issues.

[srinivasmurari]

Yes, we are using an actual proxy only.
We have tested a management API call with the proxy and it worked fine we can deploy the target server using it.

But when we are trying to use the plugin we are facing issues with the same proxy.

[ssvaidyanathan]

Are you trying the maven call from the same machine where you tested the Mgmt API?

[srinivasmurari]

Yes we have tested from the same machine where we are running the maven call

[ssvaidyanathan]

Just noticed that your proxy settings doesn't have any username password fields? Is that correct? Can you check your machine config to see if the proxy requires any authentication?

[srinivasmurari]

Yeah, it does not have a username and password.
The proxy doesn't require any authentication.

As we can make management calls from the same machine without authentication that can also conform in 100% that there is no authentication for proxy.

[ssvaidyanathan]

Are you running the direct Mgmt API calls from your machine and the same machine is failing when called via Maven? Or is it from a build server?

[srinivasmurari]

Yes we are running mgmnt API calls from the same machine and when called via maven it is failing on the same machine

[ssvaidyanathan]

You already answered that - My question is - are you trying it in your laptop? If yes, then probably your machine ldap is being passed when you make the direct API call to the proxy from your machine settings. Can you check?

I might have found something in the code but want to be sure before I make that change.