[OTHER] Investigate Azure issue #1685
Labels
🖧 Devops
Operations, monitoring, maintenance, deployment, packaging
🟨 Priority: Medium
Not blocking but should be addressed
What would you like to share or ask?
From a user feedback:
We’re having some odd issues with Taipy App deployment. The Taipy App uses the Taipy framework and has an external connection (i.e., Azure Cosmos).
Create WebApp and Deploy Taipy App using Azure CLI
a. Create WebApp resource and Deploy Taipy App ‘taipyapp2-DEV’ using the command ‘az webapp up’.
b. Results: OK. The deployment succeeds and the webapp runs without error.
Deploying a Taipy App using Azure CLI to a pre-created WebApp resource.
a. Deploy to ‘taipyapp-DEV’. (Note this is the WebApp I asked you to create yesterday. I assume the WebApp was created via Azure Portal)
b. The Azure CLI command ‘az web app up’ (the same as 1) is used to deploy, and we specify the name of the WebApp to deploy to.
c. Results: Fails during deployment because resource not found. Error states that the WebApp resource cannot be found using Azure CLI ‘az webapp up’ command. It is odd because I can list WebApp via the ‘az webapp list’ command.
Deploying a Taipy App using Azure CLI to a pre-created WebApp
a. Deploy to ‘webapp-DEV’. Note this was created a long time ago. I assume the WebApp was created via Azure Portal
b. Azure CLI command ‘az webapp up’ (same as 1) is used to deploy and we specify the name of the WebApp to deploy to.
c. Results: Fails during deployment with a build failure.
Deploying a Taipy App using DevOps pipeline to a pre-created WebApp
a. Deploy to ‘webapp-DEV’. Note this was created a long time ago and the deployment uses the build and release pipelines that you set up for us.
b. Results: Build / Deploy succeeds but App throw ‘Monkey Patch Error’ (the one I showed you before). This is an odd error because the Deployment using 1 above uses the exact same code, requirements.txt file, etc. so the only difference is the deployment method and the way the WebApp was created. Likely we need to look at the build and deploy script too.
So, we think it’s a combination of two issues:
Code of Conduct
The text was updated successfully, but these errors were encountered: