Handle JSON in Zone POST requests

[pederhan]

Checks content type before trying to call getlist on request data.

[coveralls]

coverage: 98.925% (-0.01%) from 98.938%
when pulling fdb50d1 on pederhan:zone-json-support
into fa6ca20 on unioslo:master.

[oyvindhagberg]

I tested this with mreg-cli from the migrate_to_pydandic branch (248a19e) and verified that the "zone create" commands in the testsuite work now.

[terjekv]

- zone.primary_ns = request.data.getlist('primary_ns')[0]
+ zone.primary_ns = nameservers[0]

I'm not going to pretend that I understand why we're simply picking the first one, but the PR retains behaviour and fixes the issue with content type management. That works for me. :)

[oyvindkolbu]

- zone.primary_ns = request.data.getlist('primary_ns')[0]
+ zone.primary_ns = nameservers[0]

I'm not going to pretend that I understand why we're simply picking the first one, but the PR retains behaviour and fixes the issue with content type management. That works for me. :)

It is due to

mreg/mreg/models/zone.py

Line 58 in b497579

"mname": idna_encode(qualify(self.primary_ns, self.name, shortform=False)),

We (ab)use the first name server in the list to be used as mname server in the SOA record for the zone.

The zone's primary_ns field could possibly be changed to mname to better reflect usage.

[terjekv]

We (ab)use the first name server in the list to be used as mname server in the SOA record for the zone.

Now that I know I wish I didn't know. :)

The zone's primary_ns field could possibly be changed to mname to better reflect usage.

Yep.