<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vagrant on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/vagrant/</link><description>Recent content in Vagrant on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Sep 2026 14:42:50 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/vagrant/index.xml" rel="self" type="application/rss+xml"/><item><title>HCP Vagrant deprecated: migration required in 2026</title><link>https://curadevops.metacog.co.kr/insights/2026-09-18-hcp-vagrant-deprecation-important-dates-and-migration-guidan/</link><pubDate>Fri, 18 Sep 2026 14:42:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-18-hcp-vagrant-deprecation-important-dates-and-migration-guidan/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams hosting or consuming Vagrant boxes via HCP should identify an alternative registry (self-hosted or otherwise) and plan migration before HCP Vagrant shuts down; no specific cutoff date is published yet, so treat this as a Q4 2026 planning item.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> HashiCorp sunsetting HCP Vagrant signals continued consolidation of their cloud platform away from legacy VM-based dev tooling; worth noting if Vagrant is still part of the org&amp;rsquo;s standard developer environment stack.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> deprecation mentioned (no explicit date found)&lt;/li>
&lt;/ul></description></item></channel></rss>