fix: Removing the dependency on Azure Key Vault & Truncate SQL response

[Pavan-Microsoft]

Purpose

This pull request includes significant changes to the infrastructure deployment scripts and the backend configuration. The key changes involve removing the dependency on Azure Key Vault for secret management and updating the Dockerfile for the API application.

Infrastructure Deployment Changes:

• infra/deploy_backend_docker.bicep: Added new secure parameters for azureOpenAIKey, azureAiProjectConnString, and azureSearchAdminKey, and removed the keyVaultName parameter. Updated the appService module to use these new parameters. [1] [2]
• infra/main.bicep: Updated the backend_docker module to retrieve secrets directly from Key Vault using getSecret instead of passing the keyVaultName. Removed the keyVaultName parameter. [1] [2]

Removal of Key Vault Role Assignments:

• infra/deploy_backend_docker.bicep: Removed resources related to Key Vault role assignments.
• infra/main.json: Removed Key Vault role assignment resources and updated the deployment template to use the new secure parameters for secrets. [1] [2] [3]

Dockerfile Updates:

• src/api/ApiApp.Dockerfile: Added new dependencies (opus-dev and libvpx-dev). Upgraded pip and setuptools before installing Python dependencies. [1] [2]

Backend Configuration Changes:

• src/api/common/config/config.py: Removed the initialization of the Key Vault client and the get_secret method. Updated the configuration to retrieve secrets directly from environment variables. [1] [2]

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.

[github-actions]

🎉 This PR is included in version 3.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀