You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documents/DeploymentGuide.md
+29-4Lines changed: 29 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ If you're not using one of the above options for opening the project, then you'l
147
147
1. Make sure the following tools are installed:
148
148
- [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell?view=powershell-7.5) <small>(v7.0+)</small> - available for Windows, macOS, and Linux.
149
149
- [Azure Developer CLI (azd)](https://aka.ms/install-azd) <small>(v1.18.0+)</small> - version
150
-
- [Python 3.9 to 3.11](https://www.python.org/downloads/)
- [Microsoft ODBC Driver 18](https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16) for SQL Server.
@@ -248,7 +248,32 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain
248
248
- This deployment generally takes **7-10 minutes** to provision the resources in your account and set up the solution.
249
249
- If you encounter an error or timeout during deployment, changing the location may help, as there could be availability constraints for the resources.
250
250
251
-
5. Once the deployment has completed successfully and you would like to use the **sample data**, please open a **Git Bash terminal** and run the bash command printed below. The bash command will look like the following:
251
+
5. Once the deployment has completed successfully, copy the bash command from terminal: (ex: `bash ./infra/scripts/process_sample_data.sh`) for later use.
252
+
253
+
> **Note**: If you are running this deployment in GitHub Codespaces or VS Code Dev Container or Visual Studio Code (WEB) skip to step 7.
254
+
255
+
6. Create and activate a virtual environment in bash terminal:
256
+
257
+
```shell
258
+
python -m venv .venv
259
+
```
260
+
261
+
```shell
262
+
source .venv/Scripts/activate
263
+
```
264
+
265
+
7. Login to Azure:
266
+
267
+
```shell
268
+
az login
269
+
```
270
+
271
+
Alternatively, login to Azure using a device code (recommended when using VS Code Web):
272
+
273
+
```shell
274
+
az login --use-device-code
275
+
```
276
+
8. Run the bash script from the output of the azd deployment. The script will look like the following:
252
277
253
278
```bash
254
279
bash ./infra/scripts/process_sample_data.sh
@@ -267,9 +292,9 @@ Once you've opened the project in [Codespaces](#github-codespaces), [Dev Contain
267
292
<CU-Endpoint><AI-Agent-Endpoint><CU-API-Version>
268
293
```
269
294
270
-
6. Once the deployment has completed successfully, open the [Azure Portal](https://portal.azure.com/), go to the deployed resource group, find the App Service, and get the app URL from `Default domain`.
295
+
9. Once the deployment has completed successfully, open the [Azure Portal](https://portal.azure.com/), go to the deployed resource group, find the App Service, and get the app URL from `Default domain`.
271
296
272
-
7. You can now delete the resources by running `azd down`, if you are done trying out the application.
297
+
10. You can now delete the resources by running `azd down`, if you are done trying out the application.
273
298
>**Note:** If you deployed with `enableRedundancy=true` and Log Analytics workspace replication is enabled, you must first disable replication before running `azd down`else resource group delete will fail. Follow the steps in [Handling Log Analytics Workspace Deletion with Replication Enabled](./LogAnalyticsReplicationDisable.md), waituntil replication returns `false`, then run `azd down`.
# Check and assign Storage Blob Data Contributor role to current user
50
-
echo"Checking Storage Blob Data Contributor role assignment..."
51
37
signed_user_id=$(az ad signed-in-user show --query id --output tsv)
52
38
storage_resource_id=$(az storage account show --name "$storageAccountName" --resource-group "$resourceGroupName" --query id --output tsv)
53
39
54
40
role_assignment=$(MSYS_NO_PATHCONV=1 az role assignment list --assignee $signed_user_id --role "Storage Blob Data Contributor" --scope $storage_resource_id --query "[].roleDefinitionId" -o tsv)
55
41
if [ -z"$role_assignment" ];then
56
-
echo"Assigning Storage Blob Data Contributor role to current user..."
42
+
echo"✓ Assigning Storage Blob Data Contributor role"
57
43
MSYS_NO_PATHCONV=1 az role assignment create --assignee $signed_user_id --role "Storage Blob Data Contributor" --scope $storage_resource_id --output none
58
-
if [ $?-eq 0 ];then
59
-
echo"Storage Blob Data Contributor role assigned successfully."
60
-
# Wait a bit for role assignment to propagate
61
-
echo"Waiting for role assignment to propagate..."
62
-
sleep 10
63
-
else
64
-
echo"Failed to assign Storage Blob Data Contributor role."
44
+
if [ $?-ne 0 ];then
45
+
echo"✗ Failed to assign Storage Blob Data Contributor role"
65
46
exit 1
66
47
fi
67
-
else
68
-
echo"User already has Storage Blob Data Contributor role."
48
+
sleep 10
69
49
fi
70
50
71
51
# Upload files to storage account
72
-
# Using az storage blob upload-batch to upload files with Azure CLI authentication
73
-
echo"Uploading call transcripts to storage account..."
0 commit comments