It looks like uuid_services sub-module does only deployment-related work (saves new or updated entities, which come from origin site of deployment pair). Moreover, deploy doesn't even needed on destination site while uuid_services is enabled on it.

It looks weird, so I suggest to move that module to Deployment and keep UUID only as:
1. Thing for providing unique IDs for entities.
2. Thing to export entities to features (maybe someday this should also moved elsewhere).
3. This way UUID can work on one website and do some job without Deploy.

Deploy should serve only for deployment of entities from one site to another (packaging and unpackaging):
1. Deploy should be installed on both sites (as it said in docs http://drupal.org/node/408774)
2. Deploy should have a dependency for UUID.

Comments

dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented
Status: Active » Closed (works as designed)

uuid_services is a generic purpose module. It's not tied to Deploy in any way. It just exposes a very useful API for working with entities based on UUID.

This is very thought through, because we don't want Deploy to be a requirement on the endpoint site. Deploy should be treated as a client library only, that communicates with a generic UUID Services API.

So, the uuid_services module should exist in UUID module.

The documentation you linked to is for the Drupal 6 version. And in Drupal 6 Deploy was required on both sides. However, in Drupal 7 Deploy is not required on the endpoint site. But the Drupal 7 documentation actually states so, which is wrong: http://drupal.org/node/1406134 . I will fix this.