✨ Support AI Service #630
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/major
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
The AI Service needs
To synchronize analysis reports. This requires:
Solution
Fetch Analysis Reports
Add
/analyses
endpoint with filtering onid
. Consistent with/applications/analyses
returns a sparse report (empty issues). As a policy, the hub cannot hold an Analysis report in memory because each report can be very large. The is to prevent multiple/concurrent API requests from exceeding 2G memory limit. For this reason, endpoints cannot return arrays or large resources either.Example: assumes URL encoding
A stretch goal would be to add a kubernetes (like) watch mechanism (like we did in MTV).
Perhaps:
For each resource returned, fetch the complete report using:
/analyses/:id
.Retention Policy
Add a setting to define the analysis report retention policy. This will determine when an analysis report may be archived. Thinking the policy should be expressed as the number of un-archived reports for each application (beyond the latest). Values:
A new endpoint will need to be added to archive a report (after synchronized by KAI).
Perhaps: POST /analyses/:id/archive
Commit (hash)
Add a field to the
Analysis
resource. In an effort to support both Git and Subversion, the filed would be named:commit
. For git this would be a hash.The addon-analyzer will need to set this field.
The text was updated successfully, but these errors were encountered: