Zone import cannot overwrite existing zone

[Dmitry Galkin]

Hi,

Currently it is not possible to (force-)import a zone that already exists in Designate.

There are a few problems related to it:

- If a zone export was previously done and zone file kept somewhere as a backup, than restoring it is not easy. The zone has to be deleted first and imported after deletion.

- In our case only admins can import the zone, so it becomes a two step manual process with tickets.

- Zone import can also take some time for large zones (10-30-50K records) and thus deletion of production zone before import is not desirable or possible.

Idea: it would be great to have an optional "--force" import that will overwrite an existing zone if it is present in Designate.

If that sounds like a meaningful RFE/request - we'll come up with a patch.

Thanks!

[Dmitry Galkin (galkindmitrii)]

Hi Michael,

Would you be OK with such a feature?
If nothing speaks against, we'll start the implementation.

Thanks,
Dmitry