Hi all, I'd like to learn more about usage patterns with dagger. The following cases are top of mind (Excuse the long-windedness, I have many questions):
- Deploying/Testing multiple microservices (and code repositories) as a single unit
As @winter linden mentions here, dagger can be used to orchestrate deploying multiple microservices that live in different repositories, on a test branch. (#dev message)
Is there an example somewhere demonstrating this pattern of deploying multiple microservices at once, using dagger?
- Multi-tenant application deployments
There are existing examples of using dagger to deploy different "environment" variations (i.e. dev, prod, etc.). A related problem when providing a multi-tenant service is deploying an app once-per-tenant. For example, I'd like to deploy a service (or set of services) for tenant/customer A, B, etc.
How might one achieve this multi-tenant deployment setup using dagger? I imagine the approach might be somewhat related to my first question above.
Related, some tools in the declarative infrastructure space advise keeping all of your declarative infrastructure manifests in a single repository, as opposed to keeping them "close to the app" (example: https://argoproj.github.io/argo-cd/user-guide/best_practices/#separating-config-vs-source-code-repositories).
Is it fair to say that dagger is pursuing the "infrastructure manifests live close to the app" pattern?