Queue source component when curating described.sourceLocation

[jeffmcaffer]

If a curator supplies the sourceLocation for a package, then we should be able to use that information to queue the source for the package. That requires the crawler to either

• be given this info up front
• be able to call out to the service to get the definition for the component in question

Consider also the idea of requeuing a package if a curation changing the source location is merged. This might actually be the best way to trigger the flow.

[dabutvin]

updated the title

[dabutvin]

I think we should hook on the PR being created and queue the referenced source location then
somewhere in the webhook:

service/routes/webhook.js

Line 34 in aa5148b

await curationService.validateContributions(pr.number, pr.head.sha, curations)

We should check if the curation contains a source location, check if the definition for that source location already exists, if not then queue it for harvesting

[jeffmcaffer]

Created or merged?

[dabutvin]

I think created would be best.
Someone input a commit hash, let's go harvest it.

This could help with other validation during review too

[jeffmcaffer]

Ah, I see. this is more speculative harvesting. Sounds cool. We should also do merged (or updated). The initial value may be proven incorrect and a new value entered and eventually merged. Need to ensure we get that one.