Support monorepos with microcd/projects.

[martaver]

Please describe your use case / problem. I'm investigating your microcd/projects feature and it seems incompatible with a monorepo set up.

In a monorepo, there may be many Dockerfiles scattered throughout the same repository. Many of them might change in a single commit. You don't want all of them to build and deploy every time you push. You'd only want a single service preview URL for the commit, that routes to all changed services.

Describe the solution you'd like The following features are just a start, but this would go a long way to a full-featured monorepo solution:

• allow configuring custom Dockerfile path and build context in Project resource
• share docker cache between project builds (you can use kaniko cache for this)
• pin a service preview url to a branch/pull request, so you can preview multiple projects under one URL
• introduce a path filter for Project resource that ambassador uses to check for git changes and determine if it needs to run.

Describe alternatives you've considered An example of somebody doing this set up right is Codefresh.

Additional context Monorepos are quite effective when working with large projects and, personally, are my defacto go-to. With tools like nx they're also quite accessible nowadays... I think it would be great if Ambassador could support them out of the box.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.