inf_output.json is missing and we can not make deploy of our webapp

[MYSdeployment]

Hello team,

We make a change of the instructions for the system prompt in SYSTEM_MESSAGE_CHAT_CONVERSATION and commit them to our fork. After this we tried to redeploy our working webapp to apply the changes with make deploy-webapp command but we faced the below mentioned error:

• jq: error: Could not open file /workspaces/PubSec-Info-Assistant/scripts/../inf_output.json: No such file or directory

Bug Details

@MYSdeployment ➜ /workspaces/PubSec-Info-Assistant (main) $ make deploy-webapp
Environment set: local.
Loading environment variables for local.
Loading environment variables for Language: en-US.
Loading environment variables for Azure Environment: AzureCloud.

🎯 Target Resource Group: infoasst-digitallibrary

jq: error: Could not open file /workspaces/PubSec-Info-Assistant/scripts/../inf_output.json: No such file or directory
make: *** [Makefile:28: check-secure-mode-connectivity] Error 2

Information Assistant details

Please provide the following details. You can simply include a screenshot of your Info panel as well.

GitHub branch: [e.g. main]

• main

Version or Latest commit: [obtained by running git log -n 1 <branchname>

• commit d34a580 (HEAD -> main, origin/main, origin/HEAD)

What region is your Azure Open AI Service in?

• France Central

What ChatGPT model are you using?

• gpt-3.5-turbo

model name: (i.e. gpt-3.5-turbo, gpt-4)

• gpt-3.5-turbo

model version: (i.e. 0613)

• 0613

What embeddings model are you using?

• text-embedding-ada-002

If the bug is confirmed, would you be willing to submit a PR?

What is PR?

• Yes
• No

[MYSdeployment]

Hello team,

Could you please help with the above-mentioned issue?

Thank you in advance!

[dayland]

If your codespace has expired and you were required to create a new GitHub Codespace, then this will happen. The file inf_output.json is created by the completion of the terraform deployment from make infrastructure.

If you had to recreate a new codespace, you will need to set up your local.env file again with the same parameters as you last deployment. Then at least run make infrastructure to recreate the inf_output.json file.
IMPORTANT! Be sure to examine the terraform plan before applying changes to make sure it does not want to destroy services where data resides (Azure Storage Account, Azure CosmosDb, Azure AI Search, etc.).

I would recommend that after a successful deployment you make a backup of the following files to assist you with creating a new GitHub Codespace if you need to again:

• /scripts/environments/local.env
• /inf_output.json
• infra/terraform.tfstate.d/{workspace name}/terraform.tfstate

You can then put these files back in the same location on a new Codespace to help you deploy to the same target in Azure.