<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloud-Run on PCI Oasis Blog</title><link>https://blog.pcioasis.com/tags/cloud-run/</link><description>Recent content in Cloud-Run on PCI Oasis Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.pcioasis.com/tags/cloud-run/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating from Cloud Build to GitHub Actions with Workload Identity Federation</title><link>https://blog.pcioasis.com/posts/secure-devops/migrating-cloud-build-gha-wif/</link><pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.pcioasis.com/posts/secure-devops/migrating-cloud-build-gha-wif/</guid><description>&lt;h1 id="migrating-from-cloud-build-to-github-actions-with-workload-identity-federation"&gt;Migrating from Cloud Build to GitHub Actions with Workload Identity Federation&lt;/h1&gt;
&lt;p&gt;This post documents the migration of &lt;code&gt;pcioasis-payments&lt;/code&gt; CI/CD from Cloud Build to GitHub Actions using Workload Identity Federation (WIF). It is a concrete implementation record — specific project IDs, script names, and the exact ordering decisions we made — not a general tutorial.&lt;/p&gt;
&lt;p&gt;If you want the conceptual background on WIF, read &lt;a href="./2026-04-15-replacing-gcp-credentials-in-cicd-with-wif.md"&gt;Part 1&lt;/a&gt; first. This post assumes you understand what WIF does and focuses on how we applied it.&lt;/p&gt;</description></item></channel></rss>