Is there a way to delete Billing plans in paypal sdk? - python-3.x

SDK/Library version: 1.13.1
Environment: Sandbox and Live
PayPal-Debug-ID values: None
Language, the language version, and OS: Python, Ubuntu
Issue description:
So I was wondering if there is a way to delete billing plans? I searched but I can only find for PHP and not for python.
I tried:
billing_plan.delete()
billing_plan.remove()
but none of them work
I used BillingPlan.find() to get the information about the plan so I could remove but I can't find a way to perform this action.
BTW if there isn't a way via the API let me know if I can do it via PayPal website.
GitHub issue: https://github.com/paypal/PayPal-Python-SDK/issues/295

Assuming the Python SDK doesn't offer a method for this, you could read the PHP SDK's source code to find out how it's doing it, and then implement those methods, or call the Billing Plans API's HTTP methods directly: https://developer.paypal.com/docs/api/payments.billing-plans/v1/

Related

Does Python Pulsar-Client SDK supports pulsar admin based classes?

Hi I was looking to fetch metadata of pulsar topics using python-client sdk provided by pulsar.
But i got stuck as , i was not able to find any classes regarding pulsar-admin actions like getting topics , there schema , stats etc.
Though the same things are available in java admin sdk.
example
In java :-
String namespace = "my-tenant/my-namespace";
admin.topics().getList(namespace);
link to doc :- https://pulsar.apache.org/docs/next/admin-api-topics
i need to get same set of functionally but in python sdk.
is there any way to do this or yet not supported.
Solutions Tried :-
i have tried the pulsar admin rest api's and they work.. but i prefer to go via sdk path.
The Python SDK does not have that yet.
You potentially could build a Python SDK using OpenAPI/Swagger which is available here https://pulsar.apache.org/admin-rest-api/
You could also make REST calls from Python.
You can make a request for this functionality: https://github.com/apache/pulsar/issues/new/choose
The full current documentation is here: https://pulsar.apache.org/api/python/

SAP Cloud SDK CI/CD Pipeline: Usage with non S\4 Services

I am using SAP Cloud SDK (Java flavour) to create an extension application of SuccessFactors.
I sadly discovered that the Jenkins pipeline does not allow me to use any other service than the ones listed here: SCN Blog (scroll to the Appendix).
This does not make so much sense to me, as now the SDK can be used - and it is sponsored to be used by SAP - also with SaaS in its ecosystem, SuccessFactors being one of them.
Any hint? Can this check be somehow "bypassed"?
Thanks,
Roberto.
Please note that the blog post is quite old, have you verified your assumption that it does not work with SuccessFactors API?
Nonetheless, we recently introduced a configuration option which allows you to disable certain checks, cf https://github.com/SAP/cloud-s4-sdk-pipeline/blob/master/configuration.md#s4sdkqualitychecks
checkServices is what you would want to disable in your scenario.
As stated by Florian in the comment and following the Project Piper documentation, parameters "checkServices" and "customODataServices" can be used to customize the behavior of the pipeline when running upon a non-Business Hub API.
"checkServices: false" will completely deactivated the check, whereas "customODataServices: [ yourApiName ]" will skip the check just for the specified services.

Stripe Connect is functional with Old Stripe api versions?

Dose 'Stripe connect' is functional with Stripe API version 1.18.0 ?
Version 1.18.0 of the Stripe PHP bindings will be able to use some Connect features, but not all.
Most importantly, you will not be able to use Stripe-Account header, which is the recommended way of issuing API requests on behalf of another account.
I would recommend using the latest version of the PHP bindings. Note that the syntax changed in version 2.0.0: all Stripe_Class class names are now \Stripe\Class.
All the examples in Stripe's documentation and API reference use the syntax for the latest version.

Azure Machine Learning Recommendations API: Delete Build fails

I'm using Azure's Recommendations API to generate product recommendations. I'm keeping Recommendations up to date via an SSIS package that updates the data, creates a new build for the data, and if the build succeeds, deletes any previously existing builds.
The API documentation is straightforward, and everything works fine except one call in particular fails for me returning a HTTP 406 error (Not acceptable - Accept header doesn't match a response type supported by the server).
Has anyone successfully deleted a build via this API Call?
According to the documentation a Delete Build call should look like this:
Method=DELETE
{rootURI}/DeleteBuild?buildId=%27%27&apiVersion=%271.0%27
Andrew,
I just ran into this question... Did you resolve this issue?
In contrast with most of the functions, The datamarket version of the API requires a DELETE method to actually delete a build (as apposed to a GET) -- that may be the first thing to check.
Also, I want to make sure you are aware that the datamarket version of the API will be deprecated (please read the migration guide at https://azure.microsoft.com/en-us/documentation/articles/cognitive-services-migration-from-dm/ for more details). You should now be using the Recommendations API Cognitive Service (see https://www.microsoft.com/cognitive-services/en-us/recommendations-api ).
Either way, if you are still running into issue, feel free to contact us at mlapi#microsoft.com and we can check what may be wrong with your call.
Thanks!
Luis Cabrera
Recommendations API Program Manager

Bluemix + Node.js - Is there documentation for the watson-developer-cloud module?

I am interested in playing around with the Q & A service, the demo app uses the REST API and I am wondering if the service can be used with the newer watson-developer-cloud module and if so where can I find an example or documentation for those functions.
The demo is online at Q&A Node.js demo but this uses the older REST API.
Thanks,
Andy
Yes, you should be able to use the service with the newer watson-developer-cloud module, but there's no updated demo. Note, that the module was not changed drastically enough that it should really matter.
The README.md file for the Github repository containing the project has a full set of usage instructions.

Resources