Deployment fails when a keystore or target server is added in the service callout policy about apigeetool-node

[Michael-McD]

In the interim we're using the Apigee management API which does work:
curl -X POST --header "Authorization: Basic *******=" -F "[email protected]" "https://api.enterprise.apigee.com/v1/organizations/our-org/apis?action=import&name=oauth&validate=true"

[ssvaidyanathan]

Same issue raised -
https://community.apigee.com/questions/49215/apigeetool-error-uploading-service-callout-policy.html

[Michael-McD]

Is this being investigated? I ask because I note that the original issue was raised way back in April and it still has not been resolved.

[noahdietz]

Hi all, I am currently investigating it, thanks Sai for the bump

[noahdietz]

I've found the root cause. It is an issue in the Apigee Management Server API, which means the issue cannot be completely fixed from Apigee tool. I will look into a work around for the time being while getting the fix pushed.

[Michael-McD]

Hi @noahdietz any news of either the underlying fix or temp fix being deployed?

[Michael-McD]

Hi @noahdietz any news of an underlying fix being deployed? We're trying to integrate our Apigee Proxies into our CI and have just discovered the same issue in attempting to deploy "Shared Flows" that reference a LoadBalancer .

[noahdietz]

The fix will not be released until beginning of Jan 2018. I know this is a while away, and I apologize for the inconvenience. I believe using the aforementioned bundle import API is the available workaround.

To be clear, does the issue you just mentioned WRT deploying Shared Flows + LBs occur on import or deployment of the Shared Flow? If it is the former, import, then the fix inflight should resolve that issue as well.

Again, sorry for the inconvenience.

[Michael-McD]

Hi @noahdietz, Thanx for the update. To answer your question: Shared Flow fails on import.

[anshul07]

@noahdietz any news on the fix ?

[dhayalakumarc]

Has this issue been fixed?

[noahdietz]

The fix for this was released. I will close this issue. If the issue persists, please reopen and paste any additional error messages. Thank you for following up!