allowed concurrent proccessing for plugins

[marxus]

Summary

allowed concurrent processing for plugins by copying/linking a ref of the git working state only once

Motivation

monorepo with a lot apps that uses a CMP plugin

there is a design choice on how the CMP on a sidecar is implemented
if you have a large monorepo and you trigger a refresh via a commit it will refresh all the Apps related to that repo, causing Argo to copy the entire repo N amount of times (N being the number of your apps) over to the sidecar, which causes heavy Disk I/O and basically chocking the system.

Unlike the old CMP system which didn't copy the repo N amount of times and allowed concurrent processing.

Proposal

How do you think this should be implemented?

Maybe we can have a shared volume between the repo-server and the CMP sidecar and avoid copying all the time

btw, the section about the custom plugin is the monorepo scaling considerations is misleading. with only Sidecar option on new Argo it should state sorry, no workaround for now.
https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/#monorepo-scaling-considerations