<?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 Raúl Pastor</title><link>https://pixelotes.com/tags/terraform/</link><description>Recent content in terraform on Raúl Pastor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Nov 2026 20:45:51 +0000</lastBuildDate><atom:link href="https://pixelotes.com/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>What Infrastructure as Code Is and Why You Should Adopt It</title><link>https://pixelotes.com/blog/infrastructure-as-code/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://pixelotes.com/blog/infrastructure-as-code/</guid><description>&lt;p&gt;Most infrastructure starts life as clicks in a portal. It works, until you need to rebuild it, explain it to an auditor, or find out who changed that firewall rule last Tuesday.&lt;/p&gt;&#10;&lt;h2 id="the-traditional-way-clickops"&gt;The traditional way: ClickOps&lt;/h2&gt;&#10;&lt;p&gt;For most of IT history, infrastructure was built by hand: log into the cloud portal or the hypervisor console, click through the wizard, fill in the fields, press &amp;ldquo;Create&amp;rdquo;. Then SSH into the server and type commands until it works. It even has a name now, half joke and half accusation: &lt;strong&gt;ClickOps&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>