Dear Job, We’re looking into this issue right now and will let you know as soon as we have a fix available. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC On 06 Feb 2014, at 19:23, Job Snijders <job.snijders@hibernianetworks.com> wrote:
On Thu, Feb 06, 2014 at 06:53:14PM +0100, Job Snijders wrote:
On Thu, Feb 06, 2014 at 05:31:03PM +0100, Denis Walker wrote:
Dear colleagues,
We have identified the cause of the REST API JSON issues some users have been experiencing. Details can be found on github: https://github.com/RIPE-NCC/whois/issues/114
We deployed a new minor version (1.71.1) of the RIPE Database software today at 17:15 (UTC +1) to fix this issue.
Release notes can be found here: https://www.ripe.net/data-tools/db/release-notes
It seems that the JSON structure changed. <snip>
Looking at the logs breakage seems to have started on the fourth of feburary somewhere in the morning.
I used ot be able to call mp-members in a route-set exposed through the JSON API like this:
r.json()['whois-resources']['objects']['object']['attributes']['attribute']
But now I have to access them like this:
r.json()['objects']['object'][0]['attributes']['attribute']
So the dictionary 'whois-resources' got popped and the object known as 'object' was converted from dictionary to a list?
The effect is that some of my provisioning programs are broken now, and I don't know what the expected behaviour is right now, and will be tomorrow.
Kind regards,
Job