Open Kovah opened 1 year ago
Completely agree. This is quite unfortunate. Hoping to have some activity from here again.
@jgrahamc anything you can do?
If no one ends up responding to this request, I would be happy to fork this project and maintain the SDK if people wanted to contribute to it.
I spoke to someone at Cloudflare, and they said they don't intend to update this SDK. They advised against using it and indicated that their current view of SDKs is that they don't provide a level of value that is equal to the amount of effort it takes to maintain them. They are focusing on making the APIs as easy as possible to use directly, and their recommendation is to use the APIs directly.
Thank you so much @ramsey for this information. Good to know the actual status.
I would prefer to have an appropriate notice in the repo then, but I guess this issue will provide enough insights for others.
Ahh I suppose that's an understandable response 😄. If that is the case, I suppose this repo should at least be archived with a note like @Kovah says.
I guess that's quite an opinionated discussion, so I hope ones who believe SDKs are beneficial do find value in maintaining a fork.
every good intention is punished as it deserves 👹
Sorry, I missed this tag. When me and my team are contributing we are working on a Cloudflare partner integration and I've had to use contacts inside Cloudflare to get my commits merged, which still takes a while. Their future seems to lie in Terraform and not SDKs from what I've heard unfortunately.
Given this isn't going to be updated or maintained anymore would anyone else agree that it would probably make sense to flag the package as abandoned in the composer.json file to avoid people unwittingly installing it not realising?
makes sense to me
it works (I have implemented cache purge years ago into my CMS) but it may become unreliable and can fall apart anytime soon
Filip Oščádal 🍀📱
On Sat, Apr 15, 2023, 21:08 Rick Mills @.***> wrote:
Given this isn't going to be updated or maintained anymore would anyone else agree that it would probably make sense to flag the package as abandoned in the composer.json file to avoid people unwittingly installing it not realising?
— Reply to this email directly, view it on GitHub https://github.com/cloudflare/cloudflare-php/issues/235#issuecomment-1509929485, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASMXSVUWF6YAVC3Y3GTWDXBLWZXANCNFSM6AAAAAAT5WPTUI . You are receiving this because you commented.Message ID: @.***>
Given this isn't going to be updated or maintained anymore would anyone else agree that it would probably make sense to flag the package as abandoned in the composer.json file to avoid people unwittingly installing it not realising?
@phily245 would you be able to do that?
@Kovah I've added the MR above, but we need someone at Cloudflare to do this on packagist AFAIK, @ramsey could your contact help out? I can reach out to people I know too.
https://stackoverflow.com/questions/40946151/marking-a-packagist-package-as-abandoned-in-favor-of-a-new-location as reference as to how to do this.
@jgrahamc anything you can do?
If no one ends up responding to this request, I would be happy to fork this project and maintain the SDK if people wanted to contribute to it.
I also have open MR, if you create a fork it signals I'll be happy to contribute.
The SDK works well beside few minor issues. Is anyone planning to fork and maintain? I'm willing to contribute.
"Cloudflare kind of abandoned the SDKs in favour of more accessible APIs"
Isn't that kind of the point of an SDK? to be a client to consume an API? So now everyone just has to roll their own API clients? My company services several Drupal websites that need updating to D10, the module that uses this library is sort of blocking that now.
that's the trouble with companies like Cloudflare
I have stumbled across the documentation for this on Cloudflare, confirming this as deprecated: https://developers.cloudflare.com/support/cloudflare-client-api/cloudflare-php-api-binding/
Thanks @phily245 , but even that page is now gone and redirects to https://developers.cloudflare.com/api/ . Wayback machine still has the copy though https://web.archive.org/web/20231126221026/https://developers.cloudflare.com/support/cloudflare-client-api/cloudflare-php-api-binding/ ...
It's such a shame that the decision to abandon this library was not made publicly visible via this repository.
Hi,I'm currently working on creating PHP client for CloudFlare API, ofc is far away for first release, but trying to add the most used (on my opinion) endpoints.
I am sad to see the official PHP SDK being unmaintained for such a long time. Half of the internet is powered by PHP and yet no one at Cloudflare seems to care about this SDK.
Last release and commits on October 2021. Open issues and pull requests date back to 2018.
Please, either take care of the SDK and let people help with pull requests, or mark it as unmaintained. Leaving it to rot is not encouraging for the open source community.
CC @phily245 @exportsmedia @kleisauke @levidurfee Please forward this to whoever leads this at Cloudflare.