Closed rodrigoaraujorosa closed 2 years ago
Thanks @rodrigoaraujorosa for reaching out.
Can you share the version of Apigee you are using?
A side note - The argument you are using for override is wrong. You should be using -Dapigee.options=override
That should not make any difference in the error you are seeing as the default for the deploy plugin is "override". Once I know the Apigee version, I can find out more
Hi @ssvaidyanathan we are using apigee version 4.50.00.
Thanks for the tip about the argument. Using -Dapigee.options=override, it works!!! Without the argument, it doesn't work.
@rodrigoaraujorosa - I believe if you pass the -Dapigee.options=override
, the issue should not happen. Can you try that please?
Update your mvn call to something like this
mvn install -Pmyenv -Dusername=someuser -Dpassword=somepass -Dorg=myorg -Dapigee.options=override
Also I found an issue when you dont pass the apigee.options argument with that content-type. So I went ahead and pushed a new version 1.2.4 with the fix. You can do either of the following:
-Dapigee.options=override
option
Hi,
we are trying to deploy Shared Flows, but Apigee is returning HTTP Status 415 at the time of undeploying the current Shared Flow revision. We are using version 1.2.2 of apigee-edge-maven-plugin.
Note: for proxies deploys this does not happen.
Below is our profile configuration:
Command executed:
Error returned:
When we do the undeploy test via Postman, the error does not occur, as we are not setting the content-type to application/x-www-form-urlencoded
Postman test:
I found a 2018 Issue with the same problem, but the guidelines described do not work in this latest version.
Could you help us?