Open pranavgaikwad opened 5 months ago
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
Problem
We are anticipating changes in the analyzer-lsp base image. We will split up providers into their individual images. In the enhancement, we mainly want to discuss:
Solution
See: Hub Issue for hub/addon details.
Filtering/Selection
Targets will be filtered and Providers will be selected by
Language
tag(s). This will likely depend on the Application Discovery feature.Addon Extensions
An Addon Extension is primarily an optional container definition along with criteria defined by a new CR. Providers will be defined to the hub as an Addon Extension. The first supported selection criteria will be by application tag matching.
Task Pod
The task pod will be configured with a main container for the addon and a sidecar container for each of the providers. All containers will mount an
EmptyDir
volume into /shared for sharing files such as credentials and source code trees.Custom Providers
Users may define new providers for testing using the UI by added a new Extension CR that is mapped to a new Language tag. Then, add/replace the language tag so that extension (provider) is selected.
Testing with the API is simpler. The user would add the Extension, and submit an analysis tag using the API that references the extension explicitly.
Links: