<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GCP on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/categories/gcp/</link><description>Recent content in GCP on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Sat, 26 Sep 2026 02:45:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/categories/gcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Terraform Google Provider 8.0: Breaking Changes and Upgrade Guide</title><link>https://www.cloudkaramchari.com/blog/terraform-google-provider-8-0-upgrade-guide-breaking-changes/</link><pubDate>Sat, 26 Sep 2026 02:45:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/terraform-google-provider-8-0-upgrade-guide-breaking-changes/</guid><description>
&lt;h1 id="terraform-google-provider-80-breaking-changes-and-upgrade-guide">Terraform Google Provider 8.0: Breaking Changes and Upgrade Guide&lt;/h1>
&lt;p>HashiCorp announced the Terraform provider for Google Cloud 8.0 as generally available on September 22, 2026. If you've got GCP infrastructure sitting on an unpinned &lt;code>&amp;gt;= 7.0&lt;/code> constraint, the next &lt;code>terraform init -upgrade&lt;/code> (or even a routine CI run, if you don't pin) can pull in 8.0 and start failing on resources that worked fine yesterday. This walks through what actually got removed or changed, and how to move a real config onto it without an apply going sideways.&lt;/p></description></item></channel></rss>