Skip to content

Deploying a new build stops at search service (not found) #491

@threegitty350

Description

@threegitty350

Describe the bug
Manually deploying chat copilot (new resource group) to azure is no longer possible due to the search service not being found on azure.

Specifically in the bicep file:
resource bingSearchService 'Microsoft.Bing/accounts@2020-06-10' = {
name: 'bing-search-${uniqueName}'
location: 'global'
sku: {
name: 'S1'
}
kind: 'Bing.Search.v7'
}

This prevents the setup to conclude and the app configuration fails to manifest on azure. Prior to these major changes, it did not have the issue. To circumvent this, I could comment out the quoted lines and the lines found at 670:

  {
    name: 'PluginConfig:BingApiKey'
    value: bingSearchService.listKeys().key1
  }

and installed bing search 7 manually from azure and applied the keys to the config (in azure). However, despite doing so, I could not get the app to reach a healthy state.

Platform

  • OS: Windows
  • IDE: VS Code
  • Language: N/A
  • Source: main branch (latest as of 10/12/2023)

Additional context
Deploying to eastUS. Successfully deployed many times prior September 28, 2023. Willing to try workarounds on new RGs if suggested.

Metadata

Metadata

Assignees

Labels

deploymentIssues related to deploying Chat-Copilot

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions