Did something change/break with Google Directory API over the weekend?

Question

Starting this morning, I am unable to set orgUnitPath on a User object using raw HTTP protocol.

PATCH /admin/directory/v1/users/testuser_1440432547467%40example.com

{"orgUnitPath":"/testorgunit_2"}

returns

{
  "error": {
     "errors": [ {
       "domain":"global",
       "reason":"invalid",
       "message":"Invalid Input: Inconsistent Orgunit id and path in request - 8100451664789505, /testorgunit_2"}],
     "code":400,
     "message":"Invalid Input: Inconsistent Orgunit id and path in request - 8100451664789505, /testorgunit_2"
  }
}

OrgUnit ID doesn't seem to be documented anywhere, but I'm also noticing that the data coming back from the Directory API does now include an orgUnitID property in addition to the orgUnitPath property.

{
  ...
  orgUnitId=id:02gyr1s20gshpvd,
  orgUnitPath=/
}

Can anyone confirm if there was an API change that now requires orgUnitId to be also be supplied in addition to orgUnitPath or if this is a bug that was just introduced?

Answer 1

This is most definitely a bug. For instance, the Google Apps Directory Sync tool which makes use of the API is also affected and there is not an update for the tool.