Skip to content
This repository has been archived by the owner on Apr 6, 2022. It is now read-only.

Upgrade to Symfony 3 #78

Open
jurgenhaas opened this issue Oct 20, 2017 · 5 comments
Open

Upgrade to Symfony 3 #78

jurgenhaas opened this issue Oct 20, 2017 · 5 comments

Comments

@jurgenhaas
Copy link

Are you planning to upgrade this SDK to later versions eventually? I'd like to integrate this into my DRD module (https://www.drupal.org/project/drd) which runs on Drupal 8.4 and there I can't install this SDK which requires Symfony ~2

@skwashd
Copy link

skwashd commented Oct 30, 2017

@jurgenhaas based on the recent update to the README.md I don't think this will happen.

@jurgenhaas
Copy link
Author

Thanks @skwashd for pointing me that direction. I still find it kind of weired for two reasons:

  1. This SDK lives in the Acquia namespace over at packagist
  2. There doesn't seem to be any alternative library to talk to their API

Well, for my own use case with DRD I've solved it directly as I had only a couple of endpoints to talk to and that was pretty simple. I'm just a bit confused that a company like Acquia doesn't have better API support.

@skwashd
Copy link

skwashd commented Oct 31, 2017

@jurgenhaas it is disappointing to see how Acquia have handled this. Back in 2013 Acquia were actively promoting the SDK as well as encouraging customers to use it.

I decided to write a Python library for interacting with the Cloud API. Given what has happened I'm very relieved that I fought internally to use Python instead of PHP. The code is still used daily to manage Drupal deployments at scale.

@aaronpacheco
Copy link
Contributor

I agree that it is unfortunate for this SDK to no longer be supported -- I know a number of people have come to rely on it, or were otherwise hoping to build off of it.

For additional context, the Acquia SDK was maintained as a pet project by a handful of developers at Acquia while they were still with the company, but it never really gained widespread adoption by customers, so it was never formally adopted as an official product or service. That is one of the challenging things with APIs/SDKs -- if customers don't broadly adopt them or explicitly ask for them, they tend not to get high prioritization for improvements or formal adoption in the grand scheme of things.

All I can say is that if more customers provide feedback directly to their Account Managers or our Partner Services teams about the importance of a robust, maintained SDK, or if explicit requests are made for API improvements through those channels, there's a better chance they'll land on an official roadmap at some point. I'd certainly love to see that happen, and I imagine many others would, too.

@typhonius
Copy link

I've started the process of writing a basic SDK that talks to Cloud API v2 here: https://github.com/typhonius/acquia-php-sdk-v2

I'd appreciate assistance from anyone wishing to enhance the SDK as I'm sure there are plenty of edge cases I haven't catered for.

I'm going to be using this and further developing it for the Acquia Cloud Cli command that we've been using (https://github.com/typhonius/acquia_cli).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants