How to Trigger Changes to push with deploy/provision/up

[chris-clark-serverless]

I have deployed this solution with the local version.

I can access the web app that was deployed to the azure portal.

I have made several changes locally, and then ran any 3 of these combinations, and no python/html changes are happening.

azd up
azd deploy
azd provision

[Vinay-Microsoft]

Hi @chris-clark-serverless for reporting this Issue. We will look into this and keep you posted. Can you please let me know what are the changes you made so that we can try to replicate at our end.

[Roopan-Microsoft]

Hey @chris-clark-serverless - Thanks for reaching out.

The accelerators are containerized, so when you deploy locally, the code runs from a default container, and a specific image is tagged during the process. To have your changes reflected, follow these steps:

• Push your updated code to your own container registry.
• Build the Docker image and push it to that registry.
• Update the deployed App Service to point to the new image.

Let me know if you need any further assistance! Happy to help!

[chris-clark-serverless]

@Roopan-Microsoft I'm a little confused, because the first azd up worked, and was able to package the app, and deploy the container. What are the exact commands for pushing the new code to the same container registry?

azd did all those steps initially, so it would make sense if there was some follow up steps to continually make changes, using a lot of the same variables / bicep templates, or even a shell script or azure devops yaml steps.

[Roopan-Microsoft]

Hey @chris-clark-serverless - Yes, Initial build will have the default container registry. So please follow the below steps to get it deployed to your own registry

• Create a new container registry in Azure
• Run the below commands from your terminal
• Backend
  • az acr login --name "containerregname"
  • docker build -f src/backend/Dockerfile -t "acrloginserver"/"repo":"tagname" .
  • docker push "acrloginserver"/"repo":"tagname"
• Frontend
  • az acr login --name "containerregname"
  • docker build -f src/frontend/Dockerfile -t "acrloginserver"/"repo":"tagname" .
  • docker push "acrloginserver"/"repo":"tagname"

If you feel this has more work, we are working on making these as integrated in our code, so you can handle these using a single flag during the deployment. ETA - ~1 week.

[Roopan-Microsoft]

Hey @chris-clark-serverless - Just checking in to see if you were able to achieve what you had planned and if we’re good to close this ticket.

Please let me know if you’re facing any issues—happy to assist!

[chris-clark-serverless]

Hey @chris-clark-serverless - Just checking in to see if you were able to achieve what you had planned and if we’re good to close this ticket.

Please let me know if you’re facing any issues—happy to assist!

If you feel this has more work, we are working on making these as integrated in our code, so you can handle these using a single flag during the deployment. ETA - ~1 week.

I have not done the work yet. I'm still not seeing the "end" deployment goal. Is it with azd, will i continually deploy with azd? There is an azure devops yaml file, but it is not a complete solution either. I can come up with my own way that includes the code you provided, but I was waiting for a solution which when running the bicep files, it would create the container registry itself, and deploy the current python code as is.

[Roopan-Microsoft]

sure @chris-clark-serverless - We will keep you posted for that solution.

[shafesy]

Hello @Roopan-Microsoft,

I am facing the same issue with pushing the code from local to azure, tried few things similar to what you have mentioned. it would be good to have something automated and taken care in the backend.
Shafe

[Roopan-Microsoft]

Hey @shafesy / @chris-clark-serverless - To keep you updated, we are done with the development, and we are in testing phase. Will keep you posted once its merged.

[ts46237]

It appears that the container app and app service images are coming from biabcontainerreg.azurecr.io. Is it set up for public access, otherwise how could the images get pulled?

[chris-clark-serverless]

@Vinay-Microsoft @Roopan-Microsoft how are we doing with these efforts?

[Roopan-Microsoft]

Hey @chris-clark-serverless / @ts46237 / @shafesy - Apologies for the delay. We encountered some issues while implementing it as a pre-provision hook, mainly due to permission constraints and other factors. As a result, we've revised our approach and are now implementing it as a post-deployment script. We appreciate your patience and want to assure you that we're actively working on it. We'll keep you updated.