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

[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.

[TaoChenOSU]

Hello @threegitty350,

Thanks for posting the issue!

To help us assist you better, could you let use know if you can manually create a Bing Search resource manually?

And when you say you cannot get the app to reach a healthy state, could you provide us with any errors or logs (if there are any)?

[threegitty350]

Hello @threegitty350,

Thanks for posting the issue!

To help us assist you better, could you let use know if you can manually create a Bing Search resource manually?

And when you say you cannot get the app to reach a healthy state, could you provide us with any errors or logs (if there are any)?

Yes, I was able to created it manually. I assigned the key to the configuration as a new value but it cannot start the service. Perhaps it's incorrect?

Unfortunately, I am not familiar enough with azure to provide a log.

[TaoChenOSU]

Hi @threegitty350,

Where did you set the new value to? The setting is consumed by the function app not the WebApi.

Linking this issue here to assist you further: #498. Could you also let us know your bicep version?

[threegitty350]

I think we should close this issue and resume in the other thread, it seems very much the same. #498

As mentioned in the other thread:
Bicep CLI version 0.21.1 > upgraded to > Bicep CLI v0.22.6 Did not result in a different outcome

Thanks for the support!

[TaoChenOSU]

Closing as described above.