[BUG] Fail to run `azd up`

[NanaXiong00]

Description

An error occurred when running azd up, as follows:

Repro steps

1. Run azd auth login.
2. Run azd init --template cosmos-db-table-python-quickstart.
3. Ensure that Docker is running in your environment.
4. Run azd up.

Environment

• Azd version: azd version 1.11.0 (commit 5b92e0687e1fa96dfc8292f4b900c0c58610b6a5)
• OS: windows.

Expected behavior

Run azd up can successfully.

@seesharprun and @hemarina for notification.

[Menghua1]

@seesharprun The issue occurs because the listKeys() method references the CosmosDb Account name in the main.bicep file. Since the priority of listKeys() is higher than that of the cosmosDbAccount module during the azd provision process, the cosmosDbAccount has not been created yet at the time listKeys() is called.

Suggestion:
Delete output CONFIGURATION__AZURECOSMOSDB__KEY. The key of the resource should not be output. This is unsafe. It is recommended to store and access the key in keyvault.

[seesharprun]

Suggestion: Delete output CONFIGURATION__AZURECOSMOSDB__KEY. The key of the resource should not be output. This is unsafe. It is recommended to store and access the key in keyvault.

I'm still working through this to figure out a solution. If we don't output the key, than we don't have an inner loop for local development.

[Menghua1]

@seesharprun We can store the key in Azure Key Vault and then retrieve it from Key Vault in the application.
For specific steps, you can refer to the changes in this commit: Menghua1@fba72a6

[seesharprun]

I did some more digging and realized that keys aren't necessary for this solution. The solution is supposed to use Entra auth and the use of key vault should have never happened.

All remnants of key-based auth will be removed in a PR.