<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Terraform on Erwin Staal</title>
    <link>https://staal-it.nl/series/terraform/</link>
    <description>Recent content in Terraform on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sat, 25 Feb 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/series/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Installing multiple VM extensions on an Azure VM using Terraform</title>
      <link>https://staal-it.nl/posts/azure-vm-multiple-vm-extensions-using-terraform/</link>
      <pubDate>Sat, 25 Feb 2023 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/azure-vm-multiple-vm-extensions-using-terraform/</guid>
      <description>&lt;p&gt;In a recent project, we used Azure Datafactory in a closed network and needed to access resources on-premises. That means that you cannot use the Autoresolve runtime of Datafactory. We thus used our own VM and installed the Self Hosted Integration Runtime software using a VM extension. So far, so good. We needed to install another piece of software on that VM a little later in the project. I started adding another VM extension only to find out that you can only install one VM extension per VM on Azure. We needed to find a way to install multiple dependencies on the VM using a single VM extension in a configurable and manageable way. This blog will describe how we did that using Terraform.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
