Introducing an easy way to work with Azure App Configuration in node projects
Microsoft Azure

Introducing an easy way to work with Azure App Configuration in node projects

When you’re working with building applications or services there’s always a need to store configuration. For Azure there’s a great service called Azure App Configuration that allows you to securely store, manage and retrieve configuration settings. It’s a perfect service for both smaller and larger projects and it keeps your configuration in control, and of course secured and audited. When I’m building solutions using node I typically start with storing my configuration in a local .env file and then use the dotenv package to import those settings into process.env properties. That makes it super easy to work with configurations, settings and change them as needed without fiddling through all the code and replace. Since I always add the .env file to my .gitignore I also reduce the risk of sharing secrets and passwords. When moving this from my local dev machine into Azure I have historically just used the Web App application settings. That works really great and is a simple solution to have these settings being read runtime, the web app only needs to be restarted to pick the new changes up.

Announcing the Application Insights Annotation Github Action
Application Insights

Announcing the Application Insights Annotation Github Action

When refurbishing my site and setting up Github workflows and actions I wanted to have a way to correlate any of my deployments of code to the statistics I have on the site and any telemetry/data in Application Insights. Application Insights has an API to add Annotations in your timeline. It adds an entry into your Application Insights instance at a specific time with a set of comments. This annotation is visible throughout many reports such as Sessions, Failures, Events and more, see below.