Asynchronous Zone Import
Registered by
Tim Simmons
This is related to https:/
Large zone imports (and possibly exports?) may take longer than various API timeouts due to long parsing and INSERT time. These APIs should be fully asynchronous tasks.
e.g. an import example:
POST /zones/tasks/import
202 Accepted
{"id": "<task ID>", "status": PENDING}
.. Wait 1 second... Task is NOT done
GET /zones/
200 OK
{"id": "<task ID>", "status": PENDING}
.. Wait 5 minutes... Task is done
GET /zones/
200 OK
{"id": "<task ID>", "status": COMPLETE, "zone_id": <Zone ID>}
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Tim Simmons
- Direction:
- Needs approval
- Assignee:
- Tim Simmons
- Definition:
- Discussion
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
1.0.0
- Started by
- Tim Simmons
- Completed by
- Kiall Mac Innes
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Asynchronous Zone Import
(?)