![pester app pester app](https://cdn.techjuice.pk/wp-content/uploads/2014/11/go-nawaz-go-android-app.jpg)
#Pester app windows#
It would be wonderful to be able to check those keys in a web.config (let's asume windows environment for simplicity) and compare them to my central configuration file, right? It is easy when you think about one App Service being affected and a simple application but what happens when your application is composed of multiple App Services running different parts of your application and you need to keep consistency on the configurations amongst them? a certificate is about to expire and you need to replace it or some other resource referenced by those configurations in the App Service changed to another location, changed it name or is not needed anymore and the variable in the App Service should be set to NULL. This is very strightforward and works fine, at that moment you can say that those values were correct and everything should be fine.But then. In the ideal world you have your configurations defined in some place (this can be variable groups in Azure DevOps for example or a configuration file from where you extract the correct values for your apps at deploy time) and then doing the deployment of your App Services you simply extract those values and put them in the resources you are building. For those cases you can write some test cases in pester and validate them against a configuration file with the values each App Service should have. As you start building your solution/software in the cloud, you will notice that some times web.config files (or any other configuration file) drifts from the content it had when deployed, this is not ideal but at the moment of fighting against a bug you might find yourself changing some values here and there that maybe you forget to rectify in the pipelines so next time you redeploy they get the correct values.