Skip to content

refactor: dev to main - Foundry Roles and sanitize CU output for Unicode integrity#922

Merged
Prajwal-Microsoft merged 38 commits into
mainfrom
dev
May 26, 2026
Merged

refactor: dev to main - Foundry Roles and sanitize CU output for Unicode integrity#922
Prajwal-Microsoft merged 38 commits into
mainfrom
dev

Conversation

@Pavan-Microsoft

@Pavan-Microsoft Pavan-Microsoft commented May 21, 2026

Copy link
Copy Markdown
Contributor

Purpose

This pull request introduces several improvements and new features to the deployment workflows and documentation for local development. The main highlights include enhanced tagging of Azure resource groups, the addition of scalability options for WAF deployments, and updates to documentation to reflect recent changes in the frontend stack and configuration requirements.

Key changes:

Azure Resource Group Tagging

  • All deployment workflows now automatically add or update an Owner tag (with the GitHub actor's name) when creating or updating Azure resource groups, improving traceability and resource management. This applies to both new and existing resource groups. [1] [2]

WAF Scalability Feature

  • Added a new enable_scalability option to relevant workflows (deploy-orchestrator.yml, deploy-v2.yml, job-azure-deploy.yml, job-deploy-linux.yml, job-deploy-windows.yml) to allow users to enable or disable scalability features specifically for WAF deployments. This includes input validation and parameter propagation throughout the workflows. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]

Workflow Input and Description Updates

  • Improved descriptions for several workflow inputs to clarify their purpose, updated Azure region options, and refined parameter names for clarity (e.g., distinguishing between AI and non-AI Azure regions, clarifying resource ID and web app URL inputs). [1] [2]

Documentation Updates

  • Updated the local development setup documentation to reflect the migration to Vite-powered React + TypeScript for the frontend, clarified .env configuration, updated Azure role assignment instructions, and improved layout configuration documentation. [1] [2] [3] [4] [5] [6]

These changes collectively improve deployment automation, resource governance, configuration clarity, and developer onboarding.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

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

Deployment Validation

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

Dhanushree-Microsoft and others added 24 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>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 38 out of 40 changed files in this pull request and generated 2 comments.

Comment thread tests/e2e-test/pages/HomePage.py
Comment thread src/App/package.json
@Prajwal-Microsoft Prajwal-Microsoft merged commit be1f7ed into main May 26, 2026
27 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.23.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.