[BUG] existing container registry leads to deploy.sh failed

[Elizabeth819]

Describe the bug
The first time deploy.sh failed, with a python glib missing, after installation, the second time deploy.sh failed because the first time a container registry was created. Shall I delete the storage account?

To Reproduce
Steps to reproduce the behavior:

Expected behavior
Automatically continue deployment with existing container regiestry

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[jasonclane]

There is a pull request awaiting approval that might fix your problem: #88

[jgbradley1]

@Elizabeth819 the PR that @jasonclane is referring to has been merged. Can you try again and let me know if your problem still exist? I wasn't tracking that a python glib was necessary but azure cli is a python package underneath, so that could explain the problem. We have the software requirements for deployment listed here or you can open the repo in a devcontainer which will automatically include all the required tools and appropriate version requirements.

[timothymeyers]

Closing this as stale. Possibly fixed by #88 or #106 if there was an issue.