Support the ability to connect to more than one subscription

What's missing from this now is the ability to switch the solr path based on environment.

If you rely on the DB & features you can get into a painful mess of having to do manual configuration on each environment and developers accidentally make changes to the wrong index.

The apachsolr module uses the apachesolr_path persistent variable to allow for switching of the path through $conf[].

The attached patch follows the same pattern, only with the variable name search_api_acquia_path.

Example of how to use it:

if ($_ENV["AH_SITE_ENVIRONMENT"] == "prod") {
  $conf['acquia_identifier'] = 'ABCD-1111';
  $conf['acquia_key'] = 'sdfsfsagfsadg7s8gf7asdfasd8f7sa9d';
  $conf['acquia_subscription_name'] = 'MyCompany [Dev - Solr]';
  $conf['search_api_acquia_path'] = '/solr/ABCD-1111';
}
elseif ($_ENV["AH_SITE_ENVIRONMENT"] == "test") {
  $conf['acquia_identifier'] = 'ABCD-2222';
  $conf['acquia_key'] = 'asdaksfd8798s7dafasd9f87sad9f7sa9df';
  $conf['acquia_subscription_name'] = 'MyCompany [Stage - Solr]';
  $conf['search_api_acquia_path'] = '/solr/ABCD-222';
}

There's a fair argument that this should be implemented in search_api_solr instead, however this module is implementing connect() in SearchApiAcquiaSearchService so it's not possible to use the layer below. It's not obbious to me why this is as the code in the method is exactly the same.

If you want me to push this upstream instead and you can confirm that it's ok to remove the implementation of connect() I can provide patches to remove it and reimplement this change against search_api_solr.

I've pinged various people on your behalf Alan!
(Acquia support reference #73024).

Why not use the same variables as apachesolr to make it easier and more consistent?

$conf['acquia_identifier'] = 'ABCD-2222';
$conf['acquia_key'] = 'asdaksfd8798s7dafasd9f87sad9f7sa9df';

// Regular settings
$conf['acquia_search_host'] =  'search.acquia.com';
$conf['acquia_search_path'] = '/solr/' . $identifier;

// Expert mode
$conf['acquia_search_derived_key_salt'] = '123456789123456';

On that note, this module should support the hostname that is pulled in from the subscription array.
Something similar like this.

if (!empty($conf['acquia_subscription_id']) && !empty($conf['acquia_subscription_key'])) {
    $identifier = $conf['acquia_subscription_id'];
    $key = $conf['acquia_subscription_key'];
    $subscription = acquia_agent_get_subscription($params = array(), $identifier, $key);
  }
  else {
    $identifier = acquia_agent_settings('acquia_identifier');
    $subscription = acquia_agent_settings('acquia_subscription_data');
  }
  $search_host = variable_get('acquia_search_host', 'search.acquia.com');
  // Adding the subscription specific colony to the heartbeat data
  if (!empty($subscription['heartbeat_data']['search_service_colony'])) {
    $search_host = $subscription['heartbeat_data']['search_service_colony'];
  }

  $environment = array(
    'url' => 'http://' . $search_host . variable_get('acquia_search_path', '/solr/'. $identifier),
    'service_class' => 'AcquiaSearchService',
  );

Looks good to go

Thanks for the speedy response guys.

Can you confirm that $subscription['heartbeat_data']['search_service_colony']; isn't some form of high availability failover (as the name heartbeat suggests)?

If it was I would expect it to override search_api_acquia_overrides, I can provide another patch if so.