Issue while deploying proxy via maven jenkins however proxy getting deployed successfully through GUI

Google Cloud Apigee
1

Team,

We are facing issue while deploying “Authentication” proxy via maven through jenkins. Changes done in assign message AM-Set-Profile-Exist-Status.xml policy that is in “Authentication” proxy is as below:-

AM-Set-Profile-Exist-Status.xml was existing policy and “Authentication” was existing proxy and very minimal changes were done in the policy that is removed tag from tag. and since then we are able to deploy the proxy via GUI directly but facing issues while deploying through maven jenkins.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> AM-Set Profile Exist Status emailId request.queryparam.emailId siteId request.header.X-bbb-site-id {emailId} {siteId} request.verb POST true

Errors received while deploying proxy is as below:-

[ERROR] Failed to execute goal io.apigee.build-tools.enterprise4g:apigee-edge-maven-plugin:1.1.5:deploy (deploy-bundle) on project authentication: MojoExecutionException: 400 Bad Request
[ERROR] {
[ERROR] "code" : "rest.ValidationFailure",
[ERROR] "message" : "Error occurred while validation of bean AM-Set-Profile-Exist-Status.xml. Reason: - Unexpected Repository Error null.",
[ERROR] "contexts" : [ ]
[ERROR] }
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] <a href="http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException">http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException</a>
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // stage
[Pipeline] slackSend
run slackstepsend, step null:false, desc K0ZfD9Yqx1n83lj1ahxhSWOe:false
Slack Send Pipeline step configured values from global config - baseUrl: true, teamDomain: true, token: true, channel: true, color: false
ERROR: Slack notification failed. See Jenkins logs for details.
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
2

HI @Arjun Wahi

Welcome to the community !

I copied your policy into one of my existing sample proxy and was able to deploy the code using the Maven plugin. Not sure why you are getting the error. Can you confirm that the contents in your source code system for that policy is same as the one you update in the UI which worked ? The error you reported is returned by the Mgmt server as the validation before deployment failed. Please check that and see if it works