Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This pull request removes the Azure Functions-based bot functionality and updates the infrastructure configuration for container app scaling. The changes eliminate the KITT.Bot.Functions project entirely while updating Aspire dependencies to version 9.5.1 and configuring Azure Container Apps with scaling parameters.
- Completely removes the
KITT.Bot.Functionsproject including all source files, models, and configuration - Updates all Aspire-related package dependencies from version 9.4.2 to 9.5.1 across multiple projects
- Configures Azure Container Apps scaling with minimum 0 and maximum 5 replicas for CMS API, Proposals API, and Web App services
Reviewed Changes
Copilot reviewed 31 out of 31 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| LemonBot.sln | Removes KITT.Bot.Functions project reference and updates Visual Studio version to 18 |
| src/KITT.Bot.Functions/* | Complete removal of Azure Functions project including all source files, models, and configuration |
| src/KITT.AppHost/* | Updates Aspire SDK to 9.5.1 and adds container app scaling configuration |
| src//KITT..csproj | Updates Aspire package dependencies from 9.4.2 to 9.5.1 |
| NuGet.config | Adds new NuGet configuration file with package source mapping |
| .aspire/settings.json | Adds Aspire tooling configuration specifying AppHost project path |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request makes several infrastructure and project configuration updates, primarily focusing on removing the
KITT.Bot.FunctionsAzure Functions project and related files from the solution, and updating dependencies for the Aspire AppHost. Additionally, it introduces new configuration files for NuGet and Aspire settings, and updates scaling settings for Azure Container Apps in the AppHost project.Project and Solution Structure Updates:
KITT.Bot.Functionsproject from the solution, including its.csproj,.gitignore, source code files (such asBotFunction.csand all models), and all solution configuration references. This eliminates Azure Functions support for bot-related features. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]Dependency and Configuration Updates:
KITT.AppHost.csprojfrom version 9.4.2 to 9.5.1, ensuring compatibility with the latest Aspire features and bug fixes. [1] [2].aspire/settings.jsonfile to specify the path to the AppHost project, supporting Aspire tooling.NuGet.configfile to configure package sources and mapping, standardizing NuGet package management for the repository.AppHost Scaling and Containerization:
Program.csinKITT.AppHostto configure Azure Container App scaling for multiple services (CMS API, Proposals API, Web App), setting minimum replicas to 0 and maximum to 5 for better resource management and scalability. [1] [2]Solution Versioning: