Failing tests against dev stack (329)

Thanks . That would be my fault: as part of the that PR I removed the deprecated (~7 years ago) API. I did check the DW on PUT /entity/#/version/# (I checked the wrong constant) and didn’t find any record for the past 6 months which makes sense since the API I removed is /entity/#/version (without the version number path variable). We need to restore that API. Note, maybe after 7 years is not deprecated after all ?

, so is the deprecation that the /version suffix on PUT /entity/{id} is not necessary to increment the version since the backend will automatically detect a difference and increment the version without the client forcing the increment? If so I’ll make the change in the Python client so that we can eventually retire the endpoint (but there will be the long tail of existing client deployments of course).

The (deprecated) PUT /entity/{id}/version always creates a new version. The PUT /entity/{id} has an optional parameter newVersion, that defaults to false. Even if the parameter is false a new version is automatically created when the file handle id is updated (and from next release iff the MD5 does not match, see PLFM-6429).

Backend issue.

Python tests passed.