fix: fix unit testcases

[Pavan-Microsoft]

Purpose

This pull request introduces several improvements and updates related to Azure resource configuration, authentication, and testing for integrated vectorization and batch processing. The main themes are enhanced support for managed identities, more accurate documentation, and improved test coverage and correctness.

Azure Managed Identity and Authentication Improvements

• Added support for user-assigned managed identities in Azure Search indexer data sources and skillsets, including new test cases and environment variable handling for managed identity resource IDs. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Updated test mocks and assertions to ensure managed identity client IDs are correctly passed and utilized, improving test reliability for RBAC scenarios. [1] [2]

Documentation Updates

• Updated required Azure RBAC roles in docs/LOCAL_DEPLOYMENT.md to reflect current best practices, including new roles for Cognitive Services, Cosmos DB, Key Vault, and Storage.
• Clarified local deployment instructions and environment variable usage, switching from storage connection string to storage account name for Azure Functions batch processing. [1] [2]

Batch and Storage Configuration

• Changed local.settings.json.sample and related documentation to use AzureWebJobsStorage__accountName instead of the full connection string, aligning with new configuration requirements. [1] [2] [3]

Test Coverage and Correctness

• Improved Postgres connection string handling in tests to explicitly require SSL, ensuring more secure and accurate test scenarios. [1] [2] [3]
• Added environment variable setup for Key Vault endpoint in secret helper tests to ensure secrets are fetched correctly.

Infrastructure Template Updates

• Updated Bicep-generated ARM templates in infra/main.json to reflect changes in resource configuration and monitoring workbook contents. [1] [2] [3]

Let me know if you want to dive deeper into any of these areas or need help understanding the managed identity integration in the test and resource creation logic!

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

What to Check

Verify that the unit testcases succeded.

• ...

[github-actions]

🎉 This PR is included in version 1.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀