<?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 Emily T. Burak</title>
    <link>https://emilytburak.net/tags/workload-identity-federation/</link>
    <description>Recent content in Workload-Identity-Federation on Emily T. Burak</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 10 May 2026 13:07:01 +0000</lastBuildDate>
    <atom:link href="https://emilytburak.net/tags/workload-identity-federation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure GCP auth in Bitbucket Pipelines</title>
      <link>https://emilytburak.net/posts/bitbucket-pipes-gap-gcp-oidc/</link>
      <pubDate>Sun, 10 May 2026 13:07:01 +0000</pubDate>
      <guid>https://emilytburak.net/posts/bitbucket-pipes-gap-gcp-oidc/</guid>
      <description>This is post two in my Bitbucket Woes series. Post one covered the mental-model gap between GitHub Actions and Bitbucket Pipelines.&#xA;This one is about a real pain point and cost of the gap: the Pipes ecosystem is much smaller than the Actions marketplace, and I&amp;rsquo;ve found that that gap is most painful around cloud authentication.&#xA;Bitbucket does support OIDC for keyless auth to GCP, AWS, and Azure but you BYOG - bring your own glue.</description>
    </item>
  </channel>
</rss>
