Customers automation team want an API based method to update the kustomization yaml with site-config information. The current approach hinders their parallel execution expectations.

(Avoid any common files like Kustomization
Should be an API/rest API based check in for the siteConfig)

Or have an approach that avoids git push errors when multiple clients are making git updates/changes (avoid common files)