Book Image

DevOps with Windows Server 2016

Book Image

DevOps with Windows Server 2016

Overview of this book

Delivering applications swiftly is one of the major challenges faced in fast-paced business environments. Windows Server 2016 DevOps is the solution to these challenges as it helps organizations to respond faster in order to handle the competitive pressures by replacing error-prone manual tasks using automation. This book is a practical description and implementation of DevOps principles and practices using the features provided by Windows Server 2016 and VSTS vNext. It jumps straight into explaining the relevant tools and technologies needed to implement DevOps principles and practices. It implements all major DevOps practices and principles and takes readers through it from envisioning a project up to operations and further. It uses the latest and upcoming concepts and technologies from Microsoft and open source such as Docker, Windows Container, Nano Server, DSC, Pester, and VSTS vNext. By the end of this book, you will be well aware of the DevOps principles and practices and will have implemented all these principles practically for a sample application using the latest technologies on the Microsoft platform. You will be ready to start implementing DevOps within your project/engagement.
Table of Contents (20 chapters)
DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface

OnlineMedicine.parameters.json


There are multiple ways to send parameters to ARM templates. One of the ways we saw earlier was by sending parameters using PowerShell. Another option is to send parameters to the ARM template is by way of the json file. In this json file, the parameters section contains all the parameters with their corresponding values. While deploying the template, New-AzureRMResourceGroupDeploymentTemplateParameterFile argument can be used to specify the parameters file. All parameters defined in the parameters file will be passed as parameters to the ARM template. Also, this is an ideal approach to send Azure Key Vault-related parameters and their values to the template. The OnlineMedicine.parameters.json file contains only parameters related to values that are stored in the Azure Key Vault. The vault is referred using its unique identifier, and there is a special capability provided by templates to refer to the Azure Key Vault using reference keywords.

It is to be noted...