Streamline workflow to export file entity content

Created on 19 June 2023, over 1 year ago
Updated 15 August 2023, over 1 year ago

Problem/Motivation

Export functionality treats "file" entity as any other exportable entity, meaning that "drush migrate_generator_export:export_related file file" will export a csv file dedicated to file entity content.

Same thing when exporting a media like "drush migrate_generator_export:export_related media image" with it's related content: Export functionality will export, among others, a csv for file content.

However import functionality treats files differently: no csv file is required for it. Files get process and imported when they are used among other entities: meaning that having file field specified in "media-image.csv" is enough to import both the media and it's file.

So the module is misleading in a few ways :

  • the file entity can be configured in /admin/config/content/migrate-generator-export/types
  • the file entity is exportable by "drush migrate_generator_export:export file file"
  • the file entity will be exported when including relations by "drush migrate_generator_export:export_related media image"
  • the output file entity csv file will break import"

Steps to reproduce

  • Use drush commands provided by module to export and import same content that includes a file

Proposed resolution

  • the file entity should not be listed in /admin/config/content/migrate-generator-export/types
  • the file entity should not be exportable by "drush migrate_generator_export:export file file"
  • the file entity should not be exported when including relations by "drush migrate_generator_export:export_related media image". Instead, "media-image.csv" should be generated ready-to-be-imported including related files
πŸ“Œ Task
Status

Fixed

Version

1.4

Component

User interface

Created by

πŸ‡«πŸ‡·France davidferlay

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024