Question: how do you suggest developing the migration file?

[matepaiva]

Hey, first of all, thank you for the plugin. Very useful.

I am having difficulties grasping how to develop de migration file, as it only runs once (right?). Is there a way to "dry-run" the migration file, or something like that? How is your recommended way to develop it or to debug it?

Thank you and sorry if it's a dumb question 😅

[TonyDeplanque]

For the moment, the migration is only runs once yes :)

The re-run feature is on my mind. I thought to allow re-run migration from the backoffice.
For the moment, if you want replay an old migration, you must re-create a migration file with the same content or update the migration version of the database.

[matepaiva]

Maybe a simple way to help with it is to verify if a config variable called "dry-run" is a boolean and, if it is false, it does not save the migration version on the database. What do you think?

[vesnican]

Little dirty workaround, but works:
place this function in your migration file:

resetVersion = (version) => {
  setTimeout(async () => {
    const pluginStore = strapi.store({
      environment: '',
      type: 'plugin',
      name: 'migrations',
    });
    await pluginStore.set({ key: 'version', value: version });
  }, 100);
}

and call it at the end of your migration with the number you want to reset to:
i.e. resetVersion('1'); at the end of the migration v2

Do not forget to remove it when you are done :)