In this post, I’ll show you how you can secure your secrets within your Logic Apps!
In my last post, Azure Functions - Securing resources with a function proxy, I talked about my work to develop a more Azure-centric solution to replace my current home security camera automation workflow.
Another link in the chain for me was to be able to serve up a webpage blob from my container whilst keeping the Container Access Policy set to Private.
The function proxy in the previous post enabled that, but I also then needed the webpage to be able to retrieve the video/image blobs uploaded to display them.
As you may have guessed from my last post, I’ve been quite impressed with the serverless offerings in Azure of late - as a lifelong infrastructure person, the idea of being able to throw together functional code that you can access from anywhere, without first standing up infrastructure is still a little new and surreal to me - but an experience I’m enjoying nonetheless.
I recently seen a tweet that likened Azure Functions and Azure Logic Apps as being the glue of Azure and increasingly I can’t help but share that view.
With that in mind, I thought I’d share another piece of azure glue that you might find useful - Function Proxies
Today I explore using a PowerShell function in Azure Functions to automate parts of my webapp deploment.
In my last post, Grav in Azure part 7 - Backup Solutions, I discussed backup options for a grav blog running on a D1 WebApp instance, and other possible automation opportunities.
I left off on my last post considering the use of Git-Sync to allow not only continuous deployment (which WebApps already provides - it’s how I publish already), but also backup, pushing changed files back up to the git repository (for example, if I were to write posts in the Grav Admin console, or upgrade the grav software from the admin console).