Skip to content

fix: downmerge demo from main#935

Merged
Roopan-Microsoft merged 39 commits into
demofrom
main
May 26, 2026
Merged

fix: downmerge demo from main#935
Roopan-Microsoft merged 39 commits into
demofrom
main

Conversation

@Avijit-Microsoft

Copy link
Copy Markdown
Contributor

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_scalability input/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 Owner tag 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?

  • Yes
  • [ x] No

Golden Path Validation

  • [x ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • [x ] I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Dhanushree-Microsoft and others added 30 commits May 11, 2026 15:55
…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>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
refactor: Updated Foundry Roles name
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>
feat: Enhance email template, add RG owner tag, scalability input
fix: migrate from Create React App to Vite
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.