In this video, we cover Data sources in Terraform and how we can use them to reference resources defined either outside of Terraform or in other Terraform configuration files in our Terraform files.
We also talk about Diagnostic Logs in Azure are and how we can configure Diagnostic logs in our Azure Cosmos DB account to be sent to a Log Analytics workspace.
If you have any questions, comment below or reach out to me via Twitter: Twitter: https://twitter.com/willvelida
Resources
Data Sources in Terraform: https://www.terraform.io/docs/language/data-sources/index.html
Log Analytics (Terraform Docs): https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/log_analytics_workspace#attributes-reference
Diagnostic Logs (Terraform Docs): https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/monitor_diagnostic_setting
Monitor Azure Cosmos DB data by using diagnostic settings in Azure: https://docs.microsoft.com/en-us/azure/cosmos-db/cosmosdb-monitor-resource-logs
Terraform is an open-source tool that helps us provision and manage our cloud infrastructure. With Terraform, we can automate our infrastructure management, helping us as developers to understand what is being deployed before it is actually deployed. Terraform supports multiple clouds, providing us with consistent tooling for provisioning infrastructure.
In this video, I show you how you can create databases and containers for your Azure Cosmos DB account using Terraform.
I also show you how you can use variables in Terraform to make your Terraform code more configurable across different terraform configurations.
If you have any questions, feel free to comment below or reach out to me on Twitter: https://twitter.com/willvelida
Terraform is an open-source tool that helps us provision and manage our cloud infrastructure. With Terraform, we can automate our infrastructure management, helping us as developers to understand what is being deployed before it is actually deployed. Terraform supports multiple clouds, providing us with consistent tooling for provisioning infrastructure.
In this video, I explain what Terraform is and how we can use it to provision resources, before diving into a demo showing you how to provision a Azure Cosmos DB account with Terraform!
If you have any questions, feel free to comment below or reach out to me on Twitter: https://twitter.com/willvelida
We can use Deployment Objects in Kubernetes to describe a desired state for our Pods.
In my last Kubernetes article, I talked about Pods, what their purpose is, how we can create them and deploy them using kubectl.
This article will move onto Deployments. In this post, we’ll cover:
- What Deployments are in Kubernetes
- How we can create Deployment Objects in Kubernetes
- How can we use kubectl to manage our Deployments?
- Deployment Strategies
Let’s dive into Kubernetes Deployments!
What Deployments are in Kubernetes
A Deployment in Kubernetes provides a layer of functionality around Pods and allows you to describe a desired state. …
With Azure Function Core Tools, we can retrieve settings from our Functions to simplify our local development and debugging efforts!
Before deploying our Azure Functions, it’s good to debug our Functions locally to ensure that it works as expected. Running our Functions locally requires a local.settings.json file to store our application settings.
When we first create a Function in Visual Studio, a local.settings.json file is generated for us. However, if we clone a Function app from a repository, this file won’t be cloned! (Hopefully it won’t be cloned. It’s good practice not to commit this file to your repo since it has application secrets!).
Thankfully, we can use Azure Function Core Tools to create a local.settings.json file and import our…
What are Kubernetes Pods? How can we use them to run our containers? How can we interact with them using kubectl and YAML?
After joking for a long time that I’d learn Kubernetes, I finally got serious about doing it two weeks ago. I had a chat with my boss and he encouraged me to learn something outside my domain, so it seemed like a good opportunity to finally knuckle down and get my head around it.
In this article, I’ll show you how we can perform simple operations against a Azure Cosmos DB Table API account using the new Azure.Data.Table C# SDK.
Last month, the Azure SDK team released a new library for Azure Tables for .NET, Java, JS/TS and Python. This release brings the Table SDK in line with other Azure SDKs and they use the specific Azure Core packages for handling requests, errors and credentials.
Azure Cosmos DB provides a Table API offering that is essentially Azure Table Storage on steroids! If you need a globally distributed table storage service, Azure Cosmos DB should be your go to choice.
If you’re making a choice between Azure Cosmos DB Table API and regular Azure Table Storage, I’d recommend reading the following…
Hands-on Tutorials
Using YAML Build pipelines, we can define our entire build and release pipeline in a single file!
Introduction
As part of my personal development, I’ve created a personal health platform that uses various different microservices (Built using Azure Functions) that extract data from my Fitbit account and store them in an Azure Cosmos DB database. I have other microservices that pass messages between different services via Azure Service Bus.
For this project, I use Azure DevOps to build my artifacts, run my unit tests and deploy my microservices to Azure. The great thing about DevOps is that we can do all of this with in the YAML pipeline.
Yes I said YAML. Honestly, I don’t know what the…
Assertion Scopes make our lives easier when using multiple assertions within our unit tests by saving us time and effort when finding out why our tests are failing.
Fluent Assertions is a .NET library that provides use with a bunch of useful extension methods that allow us to test our C# code in a more natural way.
Let’s say for example we are testing the output of a string. Without Fluent Assertions, we might write something like this:
string testString = "hello";
string expectedOutput = testString.ToUpper();
Assert.Equal(expectedOutput, "HELLO");If we were to write this test using Fluent Assertions, we could do so like this:
string testString = "hello";
string expectedOutput = testString.ToUpper();
expectedOutput.Should().Be("HELLO");See? Much more natural 😊
Introducing Assertion Scopes
Lets use a more extensive example. Say if I have…
In Isolated Process functions, we can use output binding to write our output of our Functions to, but they work a little differently
In my last article, I talked about how we can run our C# Azure Functions in an isolated process that decouples the version of .NET that we want to use from the version of the Azure Functions Runtime ⚡
If you haven’t read that article, you can check it out below:
One thing I didn’t touch on in that article was how bindings work in Isolated Process Functions.
In this post, I’ll explain what Bindings are in Azure Functions, How they currently work with in-process Functions and how for isolated functions, they work a little differently.
What are Bindings?
In Azure Functions, we…
Will Velida
Microsoft Data Platform MVP. Software Engineer trying to build cool stuff using .NET and Azure. GitHub: https://github.com/willvelida
