Create new offline transfer export API endpoint get an export object
In order to check on the overall status of an ongoing offline transfer export, users will need an endpoint to view an Import::Offline::Export object. Users should also have access to a REST API endpoint to see all of their offline exports.
For now, new API endpoints do not need to be made for fetching BulkImports::Export objects of each portable because they already exist at GET projects/:id/export_relations/status and GET groups/:id/export_relations/status. These will work for the first iteration of offline transfer
Proposal
GET /offline_exports/:id
Params
-
id, required, Integer - ID of the user's offline transfer export
What it does
- Get the
Import::Offline::Exportobject with the ID belonging to the current user and present it - Return an error if the new feature flag for offline transfer exports is not enabled, or there's no export record with the ID belonging to the user
- Successful responses should include the
Import::Offline::Export, whether or not it has errors, and which projects and groups are included in the export.
GET /offline_exports
What it does
- Returns a paginated list of the current user's offline exports
- Returns an error if the flag for offline transfer exports is not enabled
Edited by 🤖 GitLab Bot 🤖