<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Experimental on Pocket Developer</title>
    <link>https://pocketdeveloper.me/tags/experimental/</link>
    <description>Recent content in Experimental on Pocket Developer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pocketdeveloper.me/tags/experimental/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Learned Something - Azure Bicep Local Extensions</title>
      <link>https://pocketdeveloper.me/post/ilearnedsomething/07-30-2026-bicep-local-extensions/</link>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://pocketdeveloper.me/post/ilearnedsomething/07-30-2026-bicep-local-extensions/</guid>
      <description>
        
          
            &lt;h1 id=&#34;bicep-local-extensions&#34;&gt;Bicep Local Extensions&lt;/h1&gt;
&lt;p&gt;Azure Bicep has always been focused on the Azure Cloud. However, with an experimental feature, that is going to change.&lt;/p&gt;
&lt;p&gt;When creating resources using Infrastructure as Code, regardless of the language, the backing call is using standard API endpoints. IaC is a wrapper around API endpoints, providing readability, structure and enhancements. Terraform already provides a way to create custom Plugins for any API endpoint, and now Bicep has introduced a feature to create Extensions.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
