Create metadata rebuild task for Composer hosted repositories

[fjmilens3]

In order to recover from abnormal situations such as corrupted or deleted JSON metadata files (such as provider JSON files), we should add a rebuild task for Composer metadata to the list of scheduled tasks. This would be similar in principle to other scheduled tasks for other formats.

Note: It may be useful, for performance reasons on very large hosted repositories, to parameterize the task by vendor and project to limit the scope of the rebuild. However, it is not necessary to meet this requirement (i.e. I expect we'll have far more significant scaling issues in other ways before we reach that threshold in a periodic rebuild task).

[Elendev]

Hello @fjmilens3,

I'm using a composer hosted repository in Nexus. I've uploaded the first version of a package (1.0.0) with success and I'm using it since. I've tried to update it to 1.1.0. The package version appears in the Nexus interface but it doesn't appears in the package.json file.

I've read the issue #20 (thanks for the really great explanations !) but I'm not 100% sure it's related to this, since the uploaded version is not the same.

Anyway, would this case be covered by the rebuild task ? And if it's the case, is there a workaround to force the rebuild of the metadata ?

[bcastagna]

@Elendev Hello, I'm facing the exact same issue and I have the exact same questions. @fjmilens3 Is there anyway to rebuild manually the cache or have a workaround for this ? Even if I delete everything from the repo ("package.json", all the .zip archives products), rebooted the nexus server, it still keeps the old package.json (with version 1.0.0 in the example of Elendev)....