<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Infrastructure-as-Code on Corrupted Glitch</title>
		<link>https://corruptedglitch.netlify.app/tags/infrastructure-as-code/</link>
		<description>Recent content in Infrastructure-as-Code on Corrupted Glitch</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 18 Jul 2026 23:13:02 -0400</lastBuildDate>
		
			<atom:link href="https://corruptedglitch.netlify.app/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automating the Great Escape: Cloud Migration Pipelines with an AI Copilot in the Loop</title>
				<link>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</link>
				<pubDate>Tue, 14 Jul 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</guid>
				<description>&lt;p&gt;Every datacenter exit starts the same way: someone opens a spreadsheet with 1,400 rows, and someone else says &amp;ldquo;we&amp;rsquo;ll just lift and shift.&amp;rdquo; Eighteen months later, half the estate is still on-prem and the spreadsheet has become sentient.&lt;/p&gt;&#xA;&lt;p&gt;This is a field report from a migration that didn&amp;rsquo;t go that way — 140 production workloads moved in 11 months, zero rollback events. The difference wasn&amp;rsquo;t heroics. It was treating the migration as a &lt;strong&gt;factory&lt;/strong&gt;, not a project, and putting an AI copilot inside the loop where humans were the bottleneck.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
