@priyashikhar - my recommendation has always been to use single repo per proxy and use branches as you promote your code from lower environment up to prod. If you do not want env based branches, at least having a single repo per proxy would be easy to manage. With this you cant control the pipeline and the changes you make to this proxy. With a mono repo comprising of all your APIs, it will be difficult to find the ones that are changed and just deploy and test that. Its not impossible but just not easy either.
Take a look at this post https://www.googlecloudcommunity.com/gc/Cloud-Product-Articles/Source-Control-for-API-Proxy-Developm... for more info
LinkedIn
Twitter
