Store report to chained configmaps
What does this MR do?
- Extends main in order to add the last step in which we create chained configmaps using the base64 payload
- Introduces
configmap
package which is responsible for breaking the payload and creating chained configmaps - Extracted Configuration struct which can be used for initializing other structs. This way we don't need to have multiple argument on
New
functions. - Extended
kube_client.go
with new function to deploy a configmap. - Updated
version
function fromtrivy
package so that it returns only the version of the trivy version.
Why are we doing this?
We want to store the payload in chained configmaps. These configmaps will be read by the OCS module in the gitlab-agent.
What are the relevant issue numbers?
Overall design
gitlab-org&11968 (comment 1683845311)
Merging Order
Edited by Nick Ilieskou