<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2025-08-01-preview on Radius Docs</title><link>https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/</link><description>Recent content in 2025-08-01-preview on Radius Docs</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/index.xml" rel="self" type="application/rss+xml"/><item><title>Radius.Messaging/kafka@2025-08-01-preview</title><link>https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/kafka/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/kafka/</guid><description>&lt;h2 id="description"&gt;Description&lt;/h2&gt;
&lt;p&gt;The Radius.Messaging/kafka Resource Type deploys a Kafka-compatible
messaging namespace. On Azure, the verification recipe provisions Azure
Event Hubs with its Kafka surface enabled by the Standard tier and creates
an Event Hub named by the developer-authored &lt;code&gt;topic&lt;/code&gt; property.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bicep" data-lang="bicep"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;resource&lt;/span&gt; kafka &lt;span style="color:#e6db74"&gt;&amp;#39;Radius.Messaging/kafka@2025-08-01-preview&amp;#39;&lt;/span&gt; = {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; name: &lt;span style="color:#e6db74"&gt;&amp;#39;kafka&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; properties: {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; environment: environment
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; application: myApplication.id
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; topic: &lt;span style="color:#e6db74"&gt;&amp;#39;events&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To connect a container to the cluster, create a connection from the
Container resource to the Kafka cluster as shown below.&lt;/p&gt;</description></item><item><title>Radius.Messaging/rabbitMQ@2025-08-01-preview</title><link>https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/rabbitmq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://edge.docs.radapp.io/reference/resources/radius.messaging/2025-08-01-preview/rabbitmq/</guid><description>&lt;h2 id="description"&gt;Description&lt;/h2&gt;
&lt;p&gt;The Radius.Messaging/rabbitMQ Resource Type deploys a queue-compatible
messaging resource. In the Azure verification recipe, the platform engineer
maps this type to Azure Service Bus using the Service Bus AMQP endpoint. This
provisions the resource and maps its connection outputs; it does not prove
RabbitMQ broker API compatibility.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bicep" data-lang="bicep"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;resource&lt;/span&gt; queue &lt;span style="color:#e6db74"&gt;&amp;#39;Radius.Messaging/rabbitMQ@2025-08-01-preview&amp;#39;&lt;/span&gt; = {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; name: &lt;span style="color:#e6db74"&gt;&amp;#39;rabbitmq&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; properties: {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; environment: environment
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; application: myApplication.id
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; queue: &lt;span style="color:#e6db74"&gt;&amp;#39;jobs&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To connect your workload to the queue, create a connection from the workload
resource to the queue resource. The connection automatically injects
environment variables named &lt;code&gt;CONNECTION_&amp;lt;CONNECTION-NAME&amp;gt;_&amp;lt;PROPERTY-NAME&amp;gt;&lt;/code&gt;.
For a connection named &lt;code&gt;rabbitmq&lt;/code&gt;, the variables are:&lt;/p&gt;</description></item></channel></rss>