<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Functions on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/azure-functions/</link><description>Recent content in Azure Functions on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Nov 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/tags/azure-functions/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting Azure Function Keys with ARM Templates</title><link>https://damianflynn.com/posts/azure-iac-function-keys/</link><pubDate>Mon, 07 Nov 2022 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-iac-function-keys/</guid><description>&lt;p&gt;Today&amp;rsquo;s conundrum: I&amp;rsquo;ve deployed a new &lt;a href="https://damianflynn.com/posts/azure-functions-scaffolding/" rel=""&gt;Function Application&lt;/a&gt;, and another service needs a key to call it. API Management is a good example. The infrastructure deployment should prepare that integration without someone opening the portal, copying a key and pasting it into the next configuration step.&lt;/p&gt;
&lt;p&gt;ARM templates can create a named host key and retrieve its value through &lt;code&gt;listKeys&lt;/code&gt;. Giving the integration its own named key also makes its purpose clearer than reusing a generic default key.&lt;/p&gt;
&lt;p&gt;The examples below show the resource definition and the lookup used in my original deployment. They are fragments to merge into an existing Function App template, not a complete deployment on their own.&lt;/p&gt;</description></item></channel></rss>