Multi-Repository Setup with .NET Aspire: Best Practices for Enterprise Constraints

[mmassari]

Multi-Repository Setup with .NET Aspire: Best Practices for Enterprise Constraints

🎯 Problem Statement

I'm planning to use .NET Aspire for a new project, but I'm facing architectural challenges due to enterprise constraints imposed by our client. I'd like to discuss the best approach for handling this scenario.

🏢 Current Environment & Constraints

As a consulting company working for a large enterprise, we have the following mandatory requirements:

• Repository Structure: Each service must have its own separate repository
• Containerization: Each service repository must contain its own Dockerfile
• CI/CD: Each repository must include GitLab pipeline YAML files
  • ⚠️ Important Constraint: Pipeline YAML files reference centralized templates - we cannot modify CI/CD logic
  • Only controllable element: The Dockerfile content
• Deployment Flow:
  • Push to develop branch → Pipeline triggers → Helm deployment to dev cluster
• Infrastructure:
  • External resources (DB, Service Bus, Cache) are provisioned via Terraform on Azure
  • Secrets management through Azure Key Vault

💡 Proposed Solution

To work with .NET Aspire under these constraints, I'm considering:

1. Per-Service Repositories: Individual repos for each microservice
2. Aspire Solution Repository: Separate repository containing:
   • Main solution file
   • AppHost project
   • ServiceDefaults project
3. Multi-Repository Git Configuration: Linking everything together

⚠️ Current Issues

When implementing this approach, I'm encountering the following problems:

1. Pipeline Failures

• Each service push fails because the pipeline expects a Dockerfile that doesn't exist
• The service projects don't have containerization files when isolated
• Critical: GitLab pipelines use centralized templates that we cannot modify - our only control point is the Dockerfile itself

2. Manual Configuration Overhead

• If I create Dockerfile manually for each service, do I need to manually configure all environment variables?
• How does Aspire handle these manually created Dockerfiles in local development?
• Since we can't modify pipeline templates, all configuration must be embedded in the Dockerfile

3. Environment Variable Management

• How to properly sync environment variables between Aspire's orchestration and manual Dockerfiles?
• Integration with Azure Key Vault secrets in this setup
• Constraint: All environment setup must be handled within the Dockerfile since pipeline logic is locked

🤔 Questions for the Community

1. Best Practices: What's the recommended approach for handling .NET Aspire in a multi-repository, enterprise-constrained environment?

2. Dockerfile Generation:

   • Should I manually create Dockerfiles for each service?
   • Does Aspire have built-in support for using existing Dockerfiles?
   • How to maintain consistency between local Aspire orchestration and production containers?
   • Given constraint: Since pipeline templates are locked, how can I make Dockerfiles "smart" enough to handle all configuration needs?

3. Environment Variables:

   • Best practices for managing environment variables across this setup?
   • Integration patterns with Azure Key Vault?
   • Specific need: How to embed all necessary environment configuration directly in Dockerfiles since pipeline modification is not possible?

4. Existing Solutions:

   • Are there existing tools/approaches for this scenario?
   • Should I develop a custom publisher module to generate Dockerfiles with proper environment variable configuration?
   • Constraint-specific: Any patterns for making Dockerfiles handle complex configuration when CI/CD pipeline modification is not an option?

🔍 What I'm Looking For

• Proven patterns for multi-repo Aspire setups
• Tooling recommendations for bridging Aspire orchestration with individual service repositories
• Real-world experiences from similar enterprise scenarios
• Alternative approaches I might not have considered

📋 Technical Details

• Platform: .NET Aspire
• Cloud: Azure
• CI/CD: GitLab
• Orchestration: Kubernetes (Helm)
• Infrastructure: Terraform
• Secrets: Azure Key Vault

---

Any insights, experiences, or recommendations would be greatly appreciated! 🙏

Tags: aspire, multi-repository, enterprise, docker, azure, kubernetes, gitlab-ci

[pirimoglu]

very good case, we also work with the same setup, but I found that aspire is not supporting multi-repos yet

#10644 (comment)
#1137 (comment)