How to read the dynamic change of the image version in module.json file using the pipeline tasks, as we won’t be maintaining the previous pipeline run variable values,įor Example: In previous build we have used version of 1.0.0, now in the next commit by developer, it changes to 1.0.1. Using the Azure CLI tasks in the pipeline, we can create Layered deployment and maintain its creation and updating in the azure portal dynamically. The deployment we prefer to use in our project is Layered deployment. We have created individual tasks for the modules, the tasks internally will refer to that version of the module image as defined in the module.json file and build that version of the image and push it to the ACR. While automating this entire process through azure devops pipeline, we have used the Azure IoT Edge tasks. This way we were able to achieve the latest images running on the specified environments. Once the images are pushed to ACR, using the image tags, we create a deployment template with the tags and target the Dev/QA environment Edge devices. Using the deployment template depending on the platform (amd64, arm), we build and push the modules from visual studio. Once the local changes are done by developers in visual studio, before committing the code to the branch we use to change the module version in the module.json file of the specific module and commit the changes. We are creating the manual deployment in the azure portal using the module image versions. I have a scenario in my project, where we are having 5 IoT Edge modules (3 Backend, 1 Frontend, 1 Microsoft developed).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |