feat: integrate ipfs-repo-migrations tool

[AuHau]

Resolves: #1115

Supersedes: #2044

Depends on:

• Automatic repo migrations js-ipfs-repo#202

[daviddias]

Can we haz a test here as well (will be similar to js-ipfs-repo).

[AuHau]

@daviddias should it be part of js-ipfs or interface-js-ipfs-core?

[alanshaw]

How about --migrate option to ipfs daemon like go-ipfs?

[AuHau]

Hmmm that is a good point, but daemon is a bit too late, it would have to be part of the js-ipfs root command because you can interact with the repo without having daemon on and hence the migrations will run already during for example js-ipfs key list

Is that alright?

[alanshaw]

Gotcha, yes that makes perfect sense.

[AuHau]

Although, how it should behave? I believe that go-ipfs ask if you want to migrate your data and --migrate only automatically confirms that right?

Currently, here the migrations are automatically run because of browsers, so should that be --noMigrations instead? Which will propagate to IPFSRepo as autoMigrate=false?

[AuHau]

@alanshaw ping ^

[alanshaw]

I just meant we can leave it for now.

[alanshaw]

@AuHau and I spoke about this in IRC and decided to default to true for auto migrations in core but when run via the CLI or as a daemon it would be set to false by default, allowing the user to backup their datastore before migrating. A new global option called --migrate will set it to true.

[AuHau]

So it is ready for review. Unfortunately, I did not manage to add any tests. I am now pressed to put time somewhere else, so I don't think I will be able to work on tests anytime soon if they will be needed...

[alanshaw]

No worries, I'll pick this up from here - thanks for all your work on this @AuHau ❤️