Skip to main content


Showing posts from November, 2019

Access Azure Batch with Azure's REST API using PowerShell and AZ CLI

To start off, what is a REST API? In short, a REST API is how you programmatically interact with an application via HTTP requests. You can do things like get data (GET API call), write data (POST API CALL), and even delete data (DELETE API call). Most of the libraries or modules you work with in PowerShell are API calls. Let's see how to set up a REST API call with PowerShell and AZ CLI. Every service in Azure can be called via REST. Today as an example, we'll use Batch accounts.

What is Batch? From the Microsoft documentation: "Azure Batch runs large-scale applications efficiently in the cloud. Schedule compute-intensive tasks and dynamically adjust resources for your solution without managing infrastructure." -

Let's get started.

Pre-requisites: 1. A Batch account. To create one:
2. Access to an Azure portal
3. VSCode

The first way w…

The road to AZ-400 Azure Certified DevOps Engineer

I've decided to switch gears in my training to focus on something that I haven't before, certifications. I currently hold a Microsoft cert, VMWare cert, and Cisco cert, but I never really set out to say "I want this certification in X amount of take for this purpose.

The reason why I haven't is because I've always been more of a "jack of all trades" technology professional. Recently I've been focusing on one portion, Development Operations (DevOps). It's something that I'm very passionate about and I enjoy extensively. So what does this mean for my blog? Well, it means it won't really be changing. A lot of my content is already focused on this.

So, what's the plan? The plan is to first pass the AZ-203. Why? Because there is a pre-requisite for the AZ-400. It's either the AZ-102 (Azure Certified Administrator) which is focused more on the IT side and the AZ-203 (Azure Certified Developer) which is more focused on the development si…

Github Actions CI/CD

What is GitHub Actions? It's an API for orchestration of workflows, events, and now, CI/CD. You may be asking yourself the same question I've asked - If Microsoft has Azure DevOps for CI/CD, why put CI/CD into Github? Well, it's simple. Not everyone that uses Github uses Azure DevOps. Some use Jenkins, Octopus, or Gitlab CI. The interesting part about GitHub Actions CI/CD is the fact that it's all YAML based, just like YAML pipelines in Azure DevOps.

Now that we know what GitHub Actions is, how about we take a look at how it works? To see how it works in action, we're going to create a webapp.

Pre-requisites: 1) Azure account
2) GitHub account (free or paid)

I'm going to head over to my GitHub page and use my Cloudengineer_PowershellAzure repo.

Next I'm going to click on the "Actions" tab and scroll down until I see the "Docker image" workload. Click on "Set up this workflow".

As we can see above, this is a default YAML file.


Visual Studio Online (VSCode as a web program)

Visual Studio Online is now in public preview! What's insanely cool about this is it's a web IDE and you don't have to download anything. You can have everything on the go at all times. It's as simple as creating a new resource in Azure. Let's get started!
The first thing you'll need to do is go to the URL for visual studio online.
Click the "Get started" button and you'll be brought to a sign-in page.
Click the sign-in button and sign in with your Microsoft account. Allow the app to access your email information and click yes.

You'll be brought to an almost empty page because you currently don't have any existing environments.

Click create an environment and choose your subscription, location, plan name, and resource group. After you have chosen, click the create button.

For the next portion, choose your environment name, git repo if you have one, instance type, and how long…

Create an AKS cluster with Terraform

When Microsoft first started their partnership back in 2016, Terraform was still a new to the Software-Defined Infrastructure space. Now, Terraform is one of the most popular tools to use for this purpose. Today we're going to spin up an AKS (Azure Kubernetes Service) cluster with Terraform.

Pre-requisites 1. Knowledge of Terraform
2. Knowledge of Kubernetes
3. An Azure subscription that you have access to create resource with
4. VSCode and the Terraform extension
5. AZ CLI installed as this will be our authentication method
6. A Service Principal as we'll need a clientID and clientSecret.

The first thing we're going to do is open up VSCode and create a directory called "AKS". Within the AKS folder, create your and terraform.tfvars files.

Now that we have our configuration files set up, let's start thinking about what we need for AKS to properly run.

The first thing we need to do is ensure AZ CLI is pointing to the right place. From your terminal run;