Registry tool: store check results as artifacts

[timburks]

To support downstream analysis (e.g. scoring), I think it would be useful to store registry check results in the registry as artifacts. I'm not certain about this but am inclined to want check results in two places: at the root of the project (in a project artifact) and under an API (in an API artifact), with only project-level concerns in the project artifact (mainly issues with top-level artifacts) and everything related to APIs in the API-level artifact. That would make it easier to score APIs based on their check status. ?

[theganyo]

A check can be run on a subset of a project and for a subset of rules. How should we determine when to update these artifacts?

[timburks]

1. "for a subset of rules" If we think of check as being like a linter, we might have something comparable to a style guide in the registry that lists the default rules for the registry. Checks that use these defaults could be the ones that are written to artifacts. For the time being, we might just accept any registry check run on projects or APIs as the check we want to remember.
2. "on a subset of a project" I think the resources of interest would be primarily projects and APIs, so as mentioned above, I would like to find check results for an APIs subtree on the API. I'm not sure that I care to support directly running registry check on subresources of APIs (deployments, versions, specs), but these could run and produce output only, not attaching any results to the registry.