Closed 6a6d74 closed 11 years ago
Tag is not part of the PoC but clearly shouldn't give a 500.
[Given that the API for listing register state a point in time works then tag wouldn't be hard to add.]
Noted. I had forgotten that we had not added tagging yet. This would be useful to include in the version deployed next Thursday (if this fits with workload?). Thanks.
Done. Fixed 500 so similar omissions should give less unfriendly response.
Implemented tagging (as in the draft spec), reading tags and a minimal html UI for viewing them.
Next time I say something stupid like "wouldn't be too hard" just shoot me!
Have now been able to test this functionality - having built & deployed independent version of the Registry from source.
The release tagging works - albeit not quite as anticipated.
I have raised a new issue outlining the requirement for enhanced behaviour, and close this issue as the tagging no longer results in a 500 http response / null pointer exception.
[pre-condition: authenticated Session established]
Attempt to tag register /codes/bufr4 with tag "v17"
curl -i -b cookie-jar -c cookie-jar -X POST -H "Accept:text/plain" http://ukgovld-registry.dnsalias.net/codes/bufr4?tag=v17
The result is an internal server error: