Production Deployments

3. Lecture - About Production Deployments

Before we talk about production deployments, let us do a quick recap of what we have done till now. Our main achievement till now is that we have deployed a keyword resource to Azure successfully. We have used Azure DevOps and armed templates for that. We used Azure build and release pipelines to deploy our Arm templates from our local report to Azure DevOps. But this is just a prototype of what we will actually have in terms of production requirements for a real production environment. We will have a number of resources. Azure App Services applications,gateways, Azure SQL databases, and storage accounts. So each of these may be part of the same template for different templates. For example, you can have different templates for different services, such as a single template for keywords, another template for an App service, etc. Or you may have different templates as per your environment, such as a set of templates for your development environment, another set for non-production,and a different set for production. You can even have different templates as per the tier of your environment, such as a single template for our tier, different templates for our data tier, etc. So the idea that I'm trying to convey here is that you will have infrastructure scored up into different components or different templates,whatever may be your use case. So we have to see how we can modify our current pipeline to fit into such a real-life scenario.

4. Demo-Production Deployments - Part 1

Before we begin this demonstration, let me tell you that this is going to be a bit lengthy as compared to other lectures. The reason for this is that we will try out in real time what our mistakes will be while converting our pipelines for production deployment, in the sense that we will make deliberate errors, and I will show you how to solve those errors. So in that aspect, this is going to be a lengthy lecture. So, as I said, we have to modify our production, our pipelines for production deployment so that we can address the different scenarios, like the template, different divisions, etc. First of all, you can go to Azure and click on Add Resource Group to create a resource group on your own, if you don't already have one. Because we have previously used the keyword testargy. But I have already added resource groups. You see, I have a storage test all here and I can deploy resources to this resource group as well. So if you do not have any extra resource groups in Azure, you might want to go ahead and create them in advance because we are going to deploy to these as well. You can see that the location of this resource group is North Europe. So in this resource group, what I'm going to do is I'm going to add a new key vault, sorry, new storage account resource. I'm not going to create the resource, I'm just going to get the Arm template for this resource. So, in the same way we did for keywords, we are going to export the Arm template of a storage account and upload it to Azure DevOps and use it for deployment. So let me enter a storage account name here. You might be already familiar with this process. We can add a storage account and also let me add a name, the box storage one. Let me give the location as S and the account as K. I'm going to change to another value. For general purposes, you can give any value and replicate. I'm going to change to LRS and leave things networking. I'm going to keep it as it is. Advanced, no changes; tax, no changes. I am going to click Review and Create. It's going to validate and provide me with a template. Click on that Download template for automation button. It will open a new window where you can download a template for that storage account. Click on Download again and a zip file will be downloaded with your template and parameter file. You are already familiar with this, right? Click on that shown in the folder and extract the file. To get our template, I'm going to extract it to the same location here. So we have the extracted file with us. If you see this, it has two files, a template and a parameter file. As usual, if you open the parameter file, you will see that it is a parameter file for a storage account with its properties such as location, storage account name, etc. And if you open the template file, you will find the actual file template file JSONfile used for storage account deployment. So what I'm going to do now is to deploy a storage account to Azure using our existing keyword deployment pipeline. So, in a real production use case scenario, we are not only going to have one resource,we are going to have multiple resources, multiple templates. And for that, what we need to first do is a code push. So this is my local repo key vault where my keyword templates folder is residing.I'm going to copy these two storageaccount JSON templates to my local repository, which already has keyword templates. Let me go ahead and copy my storage account templates, the parameter file, and the template file to my local repository on my local system. I'm going to create a new folder here so that I can distinguish between keyword and storage account templates. I'm going to add a new folder, and it is storage account underscore templates. So let me rename the new folder storageaccount templates, double click, and copy the two templates files that you have copied from the other location. So for convenience, I'm going to rename these two files, which are specific to storage account as storage underscore parameters and storage underscore templates. So let me do the renaming here for storage. In order to recognise that this is the template of a storage account, I'm going to rename it "storage underscore parameters" and "storage underscore template." So now we know that this is the template for the storage account and parameter file of the storage account. Again, inside the keyboard templates folder, which we already had in here for our previous demonstration. I'm going to rename it to keyword underscoreparameters to recognise that it is the parameterfile and template of key vault. I'm going to rename it like that, keywordunderscore parameters and then keyword underscore template. So once the renaming is done, we're almost ready with our files. We have two folders in two folders. One is a keyword folder with icon template and parameter files, and the second one is a storage folder with its own parameter and template files. If you go to the Azure DevOps repository, you will see that only the keyword template folder is still there. But the names of the files are different because we have used different names for previous demonstrations. Also, if you go to your Azure account, you will see that we have not created a storage account yet. We have just exported the template and before that we used the account creation window. That's it. So what I'm going to do right now is make all these changes available in my local repository first and then push the changes to the Azure DevOps repository. Before that, what I'm going to do is create a new storage account using this storage account template. So for that, I'm going to change the name of the storage account to let us say this is the name of the storage account that I'm going to deploy. So I changed the name in the parameter file. Then what I'm going to do is already have the keyword pipeline working. So along with this deployment, I'm going to also add a new key vault along with the storage account. So for that, I'm going to rename my keyboard to let us say, "DevOps test KV 1230r." Let us keep it at three to one to make sure that it is a globally unique name. So I saved these two files, the template and the parameter file. So we have a lot of changes. We have added folders via files and editor files,so do a gift status and you can see that in tracking all those changes. Now, if you do a git add A, you will add all these file changes to your local repository. So do it like this: git add a let me type it out, okay?git add A to add all these file changes. Now what I'll do is I'll make it a local commit I'm going to add storage templates and modify templates to the commit message. added storage account templates and modified existing keyword templates. So it's a local commitment. I'm going to do a git push and allmy changes that I have made till now willbe available in my Azure DevOps repository. So if you go to Azure DevOpsappear now, you can see that. Let me go there and show it to you. Let me reload the page first. So if you reload the page, you can see that it has changed. The folder view structure is changed. We have the keyword templates with their named keyword templates and parameter files and the storage account template with the new storage account template and parameter files available in the local Azure DevOps remote repository. If you go to pipelines, what we used to do is trigger the build pipeline.But in our previous demo session we enabled CACD. So that is the reason. You can already see that there is a build that was triggered immediately after the code push that is using our latest committee storage template, modified keyword template, but you can see that the build failed. Why did the building fail? working fine. We have not made any changes to the storage account as of yet. At least a keyword section should work fine, right? You can see that the erroris template file pattern was not found. And if you go to release, you can see that no release got triggered. Why? Because the police can trigger the build only if the build is successful. Release seven is the previous release that we triggered and your leads do not get triggered because the build failed. Now we have to investigate why the building failed. So if you go inside the build pipeline, inside that particular keyword We have not added the storage account task yet, but the failure that we have is for the keyword deployment task. So if you go inside the keyworddeployment task, you can see that the resource group allocations are all fine. But if you scroll down, you can see the template file which is being referred to in the keyboard template file. But do we have that file available now? We don't have why. Because we renamed the file to keywordunderscore template and keyword underscore parameters, So that is the reason that the bill failed. So let me edit these two, these two templatesand parameters, and make the keyword section perfect. First of all, let me edit the templatefile, browse to the new template, rename the templatekeyword template file under the keyword underscore template folder I'm going to search for keyword underscore template JSON and templateparameter file. I'm again going to edit that to search for the new keyword parameter file. keyword parameters in JSON. So I'm going to save my changes and that would have sold our keywordbuild pipeline issue and then what is remaining. Keep in mind that we are still giving them modest validation only. Now what I'm going to do is I'm going to add the storage account validation into this build pipeline. Now the build pipeline is validating only the keyword template. So let me add a new task here. Click on that plus icon and search for resource group deployments. resource group deployments. Click on add, then click on that task again to let us fill it in with the values. Change the display name to storage account deployment. Let us keep it as storage account validation, which is more meaningful because we are not deploying when we are building, right? So let's see if it is account validation. Give us template validation. Storage account template valuation Under our subscription, you can select the service connection that we have defined before. The configuration is very similar to the previous keyword task configuration. So you can choose any existing resource group as a resource group. As I said, I have a different purpose. I'm showing it to a different resource group. If you want, you can deploy to the same resource group. So I added storage tests and I'm using the location of that resource group as Europe, which is the exact location of the resource group that we have in Azure. So now location I have now let me go ahead and choose the template file for the storage account, which is under storage account under the templatefolder storage underscore template. Then let me go to the parameter section and select the parameter file parameters and deployment mode because we are only doing validation. Let me change that to Validation only. And let me click on Save. So that is the space that we have. That is where we add the storage construction. Now, one more change I want to make is to rename the keyword deployment to that meaningful name, keyword template Validation. Let me make that change. Also, there's the display name that we are changing here. Keyboard template validation. Let me click on Save and save it again.

5. Demo-Production Deployments - Part 2

So we are almost done with our building pipeline now. So, if you go to leases, you'll notice that we haven't yet entered the release pipeline to add the storage account section, correct? We are not adding a storage account deployment section. So if you go to stage one underkeyboard deployment, and if you click on plus storageresource group deployment, click somewhere else. Let me go to the release pipeline again. Let me click on edit. Let me click on this. Click on Edit Edit on the list pipeline and I'm going to disable the continuous deployment rigour temporarily. Okay? Let me click on save, then click on okay. Before we actually edit the build pipeline, I'm going to build the build pipeline first because the build pipeline is first and I do not want the release pipeline to get triggered. That is the reason I disabled the release pipeline. So I triggered the build pipeline right now and I'm going to explain why we are triggering the build pipeline to make the artefact sources available to the release pipeline and why we are doing that. Because the release pipeline takes the artefacts from the build pipeline, we have modified the build pipeline to add the storage account section. So the building pipeline is completed right now within ten to thirteen seconds. Now we have the storage account artefacts also available to the release pipeline. Previously, we only had the artifacts' keywordtemplates. The template artefact which we had earlier was the keyword one only. So let me add a new storage account inside the release pipeline right now. So let me search for resource group deployment again. Resource group deployment I will click on add. I am going to configure this again. Let me change the displayname to "Storage account deployment." You understood the point, right? We caused this by disabling the continuous deployment component of the release pipeline. So let me change the display name here and I'm going to add the AJ subscription service connection and the resource group and the location again, which you will already be familiar with. So we changed. We had only the keyword artefacts available before. In order to add the survey on artifacts, we triggered the build pipeline again. What did we do? We made these storage account artefacts available to the release site. So let me choose the resource group and the location again as North Bureau. Again, the same set of configuration steps north of the location, and you can see here that the storage in the property section is the reason I'm using North York here. Okay, so he's trying to select our storage account artifacts. If you browse to the template section and if you search for the linked artefacts inside the folder drop, we do not have them. Why do we not have it? Only the key volt template and parameterartifacts are available here, not the storage account ones. So what are we missing? So let's think about it. Why are we missing the storage account section? Here's what needs to be changed in the build pipeline to make the storage account template available as artefacts in the release pipeline. So we already have a keyword. What do we do for the keyword section to make the artefacts available? So let me cancel my release cycle and go to the build pipeline to make it a service account. So if you see here, we have added a new task, publishartify, and the task to publish. We assigned the keyword templates folder to that task. Did we add any section called "storage account templates" where ourstorage account templates are decided? No right? So then, if you are not adding how it can access a storage account template pack source, go to the build pipeline again and edit it and add a new task Publish the artefact and click on Add again. We are going to again notify the build pipeline to add a new task and make the path to publish a storage account template. So we have the two template and parameter files inside. We chose that artifact's name. You can keep it as a drop. So we have two published artefacts now. One for the storage account and one for the key vault. Click on Save and queue the build pipeline again. Why are we queuing? Because we want to make the artefacts available with the new pipeline now, we have made a change to add the artefact source to add the storage account templates available to the release plan. So we have to trigger the building pipeline. So let's wait for the building pipeline to be completed and come back once it is completed. So that is the change that you have to make. You also have to make the artefacts available. So the building pipeline is in progress. It will already take 15 to 15 seconds. Okay, it's completed. Now you can see that both artefact drops are completed. Now you can go to the release pipeline and click on Edit. Remember that we have disabled the continuous deployment trigger. So even the successful build is not triggering the release pipeline. So what is inside the release pipeline? Click on Add and add a new task for the resource group deployment. So we have added the new task. Now I'm going to change the display name of the new task again. same set of configuration steps for storage account deployment. I change the display name to that particular name as your subscription I'm going to choose the service connection that we had before under the source group. Let me choose the storage test RGresource group that we have used before. Let me storage test RG and for the location, the location of the resource is North Europe. Let me choose that location and inside templates, click on browse again to link to the Architects folder dropfolder. Inside that, you can see that we have the storage parameters under the storage template available. So choose the template file and the parameter file for the storage account. This is the reason that we have added an extra task to the build pipeline. Now let me search for the parameter file of the storage account as well. Now we have them available after the build pipeline is successful and the parameters are now in the deployment mode. You can keep it as incremental itself and you can do that with our release pipeline. Now click on Save. Click on "okay." And now if you want, you can directly create a release from here itself or from the laser window. You can release now that we have our Bill pipeline already completed. Either you can enable the continuous deployment trigger and again run the build pipeline so that it will come and trigger the release pipeline, or you can keep it disabled. I'm not going to enable it. Let's enable it here. Let's go to the building pipeline again. So we have enabled the deployment. I think we do need to run the building pipeline again, right? We will directly create a list directly.So it has been triggered. You understood the point, right? Why are we not creating a building again? because we have the building cycle already completed. So I enabled continuous deployment in the release cycle. But I'm not going to trigger the build again. I can directly trigger the release, right? because the building was already completed. Why? To wait for the building to be completed again complete.So I have triggered the release directly and I'm waiting for completion. It again resulted in an error. So what is the error? The error is not in the storage account deployment. It did not get triggered. The error was in keyword deployment. So if you go inside the lease pipeline, what is the error that we have here inside the keyword deployment task? You can see that the template and the parameters it's referring to are the old value. Why? because we have changed only the build pipeline for the renamed values. The renamed parameter and template files are available as the artefact after the build pipeline is completed. So let me change that in the keyword section as well. This is one of the major mistakes that people make. They forgot to change the release pipeline. So let me update the template and parameter files with the rename values for the keyword deployment task. Click on "okay." And I'm going to trigger the release again. I'm only going to trigger the release because Bill was already successful. because we changed the build pipeline. It was perfect. The lease pipeline was missing the updated values and I changed them and triggered the release pipeline again. So let me wait for the release pipeline to be completed. You can see the log is getting initialised and artefact download is in progress. The Keyword deployment task is running. So let us come back once the doc is completed. So it's completed. Now, keyword deployment. You can see that both of them were successful if you go to the Azure Portal. Now let me go to the Azure Portal. Inside the storage test RG that we have defined, you can see that a new storage account is created with the parameters and templatefiles that we have specified before. And if you go to the other resource group, remember that keyword deployment is taking place in another resource group. That is the KV test.RG Resource Group KV Test RG Resource Group So if you go inside that resource group, you can see otherkeywords are there, which were used for the previous demonstration. You can see that a new keyword with the name that we use for this deployment. DevOps just KV three, two, one that is also deployed. So this is how you enable multiple deployments to multiple resource groups or environments, as well as multiple tears, and so on.

6. Demo-Production Deployments - Part 3

But we are not done yet. We still have a problem. That is the problem. If you go inside the build pipeline, you can see two tasks, and for each task you are adding a published artefact browse section. So what if what happens if you have 100 templates or let's say 25 templates, you cannot go and add one for each template? You can't add thispublish artefact drop to every template. So for now, we have two templates. We have to publish artifacts. So we have to solve that issue. We cannot have 100 artefact deposit tasks for that. What I'm going to do is I'm going to add a new folder here in my local depository. I'm going to change the name of the folder to Arm templates, and I'm going to copy these two keyword templates and the storageaccount template file inside that Arm templates folder. So let me copy it to the Arm templates folder. Now, in our repository, local repository, we only have one folder, and that is the Arm template. So before we push the code, I want to disable the continuous integration trigger to just show you how to manually trigger the build pipe. And I'm going to disable the continuous integration because if we push directly it is going to again trigger the build pipeline. We have to again modify the building pipeline according to the change that we just made in the local report. So let me go ahead and disable the continuous deployment and continuousintegration. Check out continuous deployment disabled. Let me click on Save again. So I have disabled the continuous integration from the build pipeline and the continuous deployment from the release pipeline. You can see that the rapper has not yet updated. Our repo now contains a main folder which is Arm templates. At a storage account deployment, you must create subfolders for keyword deployment. That is how we have it. That is how we change the folder structure inside the local repository. So I'm going to edit my keyword template again and rename it to another value. Let me change it from three to one and click on Save. So I'm going to deploy this new keyword with my new deployments and let me change the parameter file of the storage account to another value. Let us change it to Devopsist 3123. Let us also add something new here. So this is the new storage account that we are going to deploy. And if you come here, you can see that the repo still contains all the folders. So let me make a code push to this using this new folder structure. I'm going to upload that folder structure to Azure DevOps. So let me add the gift status. You can see that Git is tracking our file changes, so let me do a Git add to add all of those file changes and a Gitcommits M with a production deployment commit. I made a mistake. What was the mistake? Okay, I missed the message git commit I was supposed to give. I did not try that part. So let me add that part. Git commits them, and the commit says production deployment final commits. So do a git push. Now I have done the git push. I'm going to let me scroll this up and show it to you. Okay, I'm going to do a git push. It is going to upload all those updated folder structures to Azure DevOps. Now if you come and reload the page, you'll see that it's waiting for the page to reload. You can see that now it contains only one folder named "arm templates" with two supporters keyword and storage account templates. Now you can see that the build pipeline did not get triggered automatically. Why? We have to make some changes again because we disabled the continuous integration. The first change that we have to make is that we have to update the template path because we added a new folder. The template path is again changed. You will already be familiar with this. We have discussed this live demonstration of error. Change the template path to inside thatfolder. keyword templates. keyword underscore. template audition. Now again, change the parameter path to include that new folder Armtemplates folder that we uploaded. Change the parameter path. Also, let me click on okay and make a similar change in the storage account template section as well. Go and change the storage account path under the Arm template folder storage account template storage template JSON and change the parameter file as well under store templatestorage account templates storage account parameters JSON. So make those changes. Now we have to publish the artefact drop. The reason why we change the folder structure is to avoid it. So let me browse and choose the Arm templates folder as the single path for the artefact row, which includes both the keyword templates and storage account templates. Now we have it only as a published artefact drop file. You can remove the second task and click on save. I'm going to save and directly queue. I'm going to click on "Save and Queue." Or let's click on save right away. I'm going to queue my build pipeline. Why? Because we are triggering it. Because to make these changes available in the artifactrepository profile so that we can in the editorial pipeline,we will have the artefacts directly available. So you can see that it took the final push. Let's wait for the bill pipeline to be completed. I'm doing the check out now. Keyword template validation is in progress. Storage account validation is in progress. Publish Artifact It's completed hardly all the seconds it took. Now you can go to the release pipeline and make the same set of changes in the release pipeline. You have to update the new artefacts in the release pipeline. So remember that continuous deployment is disabled. That's the reason that it did not get triggered automatically. So go inside the keyword deployment In releasepipeline, search for the template artefact template file. I should say go inside and you can see that there are two new folders under the blog. Deployment and service account deployment search and select the keyword template JSM for the template artefact. For the parameters, select the keyword parameters JSON as the artefact file let me select key via metersJSON and storage account deployment. I'm going to change the template file again to Storage account deployment template JSON and the storage accounttemplate folder storage template jason and let me select that and for the parameters, I'm also going to change the storage account parameters JSON. So we are almost done. The only thing left is to let me select the service parameters in JSON The only thing left is to trigger the release pipeline. So click on okay and click on create leads. So let me click on "Create list." Click on Create and our list of ten has been created. So this is it. We are almost done with the product. We can integrate production deployment. Once this is done, if you want, you can enable the CACD back again so that a code push will result in an automatic build and release just for demonstration purposes to avoid conflicts and automatic triggering. I just want to show it to you in a live demonstration. So while the release cyclone is running, if you go inside the build pipeline, you can say that it's more of a structured form now. And if you go to the post, you will see that you have a folder for Arm templates. You can add a number of templates inside this and if you have other files such as PowerShell or your CLI files, you can create a separate folder for them and like select similar to error ontemplates, you can create a separate folder there as well to add the power supplies and CLI scripts. So go inside the release pipeline. Let's wait for the release pipeline to be completed. The keyword deployment task is still running. It's come to that once it is done. So the release pipeline was completed. If you go to the resource group now and press enter, you will see that a new keyword has been added appended within, which was a file change that we made. And if you go to the other resources,what is the other resource group's name? Storage test: it's so inside that you can see that we have a new storage account with a storage test. New one, two, and three.

ExamSnap's Microsoft AZ-400 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Microsoft AZ-400 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.