fix: downmerge demo from main#935
Merged
Merged
Conversation
…and configurations - Changed project structure to support Vite as the build tool. - Updated package.json to replace react-scripts with Vite and adjusted scripts accordingly. - Removed public/index.html as it is no longer needed with Vite. - Updated environment variable access from process.env to import.meta.env. - Modified TypeScript configuration to target ES2020 and updated module resolution. - Removed reportWebVitals and adjusted testing setup for Vitest. - Added Vite configuration file for server and build settings.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…nal ports and environment variable prefixes
…v.production for API base URL
Agent-Logs-Url: https://github.com/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator/sessions/ded6036c-43b4-462c-b7a0-f8c5483b6a1f Co-authored-by: Dhanushree-Microsoft <250931221+Dhanushree-Microsoft@users.noreply.github.com>
…edge-Mining-Solution-Accelerator into km-gen-depdh # Conflicts: # src/App/package-lock.json
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
refactor: Updated Foundry Roles name
… and setup scripts
The Content Understanding analyzeBinary API (v2025-11-01) intermittently corrupts Unicode characters by stripping the high byte (e.g. U+2019 -> U+0019). This causes apostrophes and quotes to render as box characters in the Citation Panel. Added _sanitize_cu_output() to map known corrupted control characters back to their intended Unicode equivalents after CU processing, before saving to Search/SQL. Fixes AB#43310 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ping Agent-Logs-Url: https://github.com/microsoft/Conversation-Knowledge-Mining-Solution-Accelerator/sessions/50f2a621-4990-4aca-8dd8-cfa5ea31ce6f Co-authored-by: Yamini-Microsoft <191316559+Yamini-Microsoft@users.noreply.github.com>
feat: Enhance email template, add RG owner tag, scalability input
fix: migrate from Create React App to Vite
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.
Purpose
This pull request introduces several improvements and new features to the deployment workflows and local development documentation. The main enhancements include adding support for scalability features in WAF deployments, improving resource group tagging and management, refining deployment parameter validation, and updating documentation to reflect recent frontend and Azure role changes.
Workflow Enhancements:
Added a new
enable_scalabilityinput/parameter to deployment workflows (deploy-v2.yml,deploy-orchestrator.yml,job-azure-deploy.yml,job-deploy-linux.yml,job-deploy-windows.yml) to enable optional scalability features for WAF deployments. This includes validation and propagation of the parameter through job inputs and environment variables. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]Improved resource group creation and management in deployment workflows by ensuring an
Ownertag is added or updated based on the GitHub actor, both when creating new and updating existing resource groups. Enhanced output and error messaging for better traceability. [1] [2]Parameter and Validation Improvements:
Strengthened input validation for boolean parameters (e.g.,
enable_scalability,waf_enabled,EXP) in deployment workflows to ensure only valid values are accepted, with clear error messages for invalid input. [1] [2] [3]Updated deployment parameter descriptions and available Azure regions for improved clarity and accuracy, especially for frontend and AI project resource IDs, log analytics, and test options. [1] [2]
Documentation Updates:
Updated local development setup documentation to reflect that the frontend now uses Vite with React and TypeScript, clarified port usage, and improved environment variable descriptions. [1] [2] [3] [4] [5]
Corrected Azure role assignment instructions to use the "Foundry User" role instead of "Azure AI User" for AI Foundry access.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information