<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workload-Identity-Federation on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/workload-identity-federation/</link><description>Recent content in Workload-Identity-Federation on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 09 Apr 2026 22:58:47 -0500</lastBuildDate><atom:link href="https://startaitools.com/tags/workload-identity-federation/index.xml" rel="self" type="application/rss+xml"/><item><title>Firebase Migration Debugging Saga, GWI PR Reviews, and the Bounty Proof Wall</title><link>https://startaitools.com/posts/firebase-migration-debugging-saga-bounty-proof-wall/</link><pubDate>Sun, 18 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/firebase-migration-debugging-saga-bounty-proof-wall/</guid><description>&lt;p&gt;Thirty-six commits across three repos. The Firebase migration ate most of the day &amp;ndash; not because the migration itself was hard, but because CI kept breaking in new and creative ways. The GWI and bounty work shipped cleanly by comparison.&lt;/p&gt;
&lt;h2 id="firebase-migration-the-plan"&gt;Firebase Migration: The Plan&lt;/h2&gt;
&lt;p&gt;The intent-solutions-landing site was on Netlify. It worked fine, but having the company landing page on a different platform than everything else (Firebase) meant two sets of deployment configs, two DNS management interfaces, two SSL certificate renewal processes. Consolidation to Firebase Hosting was the goal.&lt;/p&gt;</description></item></channel></rss>