<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pulumi on Erwin Staal</title>
    <link>https://staal-it.nl/tags/pulumi/</link>
    <description>Recent content in Pulumi on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sun, 12 Mar 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/pulumi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating reusable modules with Bicep, Terraform or Pulumi</title>
      <link>https://staal-it.nl/posts/modularizing-iac-bicep-terraform-pulumi/</link>
      <pubDate>Sun, 12 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/modularizing-iac-bicep-terraform-pulumi/</guid>
      <description>Over the years, I’ve been working with several infrastructure as code tools. One of the things that I always find essential, no matter the tool, is to write readable and maintainable code. One way to do that is to create a proper structure for what you are building. All of the IaC tools I have used allow you to modularize your code somehow. A module is a piece of code responsible for one specific thing.</description>
    </item>
    
  </channel>
</rss>
