Rethinking an old Logic App deployment package – part III

Previously in Note to self…

I’ve been discussing how I’ve leveraged Jeff Hollan’s Logic App Template Generator and some PowerShell goodness to export a ARM templates to all Logic Apps in a specific resource group. You can read about that here.

Linking ARM Templates together

Azure Resource Manager templates have the ability to link templates, creating a “parent-child” or “nested” relationship, allowing a single template to deploy resources that are defined in various individual templates. The advantages of this technique in my opinion are:

  • Each resource can be defined in isolation, which makes maintenance of that resource simpler.
  • Related components can be grouped in “parent” templates for a simpler deployment experience, but they can still be deployed individually if required.

This was exactly the type of solution I was looking for, after having to deal with the pain of replacing a logic app template in the middle of a monolithic ARM template containing another 15 templates. That would usually take a couple of hours to make sure that the template was replaced correctly and nothing was removed that would make the deploy to break. Continue reading “Rethinking an old Logic App deployment package – part III”

Rethinking an old Logic App deployment package – part II

Previously in Note to self…

I’ve been discussing how my first Logic App deployment package was not exactly what I’ve envisaged. So when I had a chance to revamp it, I jumped into the opportunity. You can read about that here.

Logic App Template Generator

I’ve decided to use Jeff Hollan’s Logic App Template Generator – a PowerShell utility that Jeff created sometime ago and have made available on GitHub. Jeff’s PowerShell module have a two cmdlets: Continue reading “Rethinking an old Logic App deployment package – part II”

Rethinking an old Logic App deployment package – Part I

Some time ago I had the opportunity to work on a big Logic Apps implementation. The project was a big success and I’ve learned a lot… but one thing always bugged me on that project: the way I’ve tackled deployment. It was a mix of me, my team getting used to logic apps and the tooling still on early stages.

Almost a year later and I have the opportunity to revisit this deployment setup, as I’m working on some updates in the logic apps. So I’m taking this opportunity to try to create the deployment package the way I think it should be. My plan is to document the new “thinking”, any gotchas and tools I’m using along the way. So expect a series of blog posts as this evolves. Continue reading “Rethinking an old Logic App deployment package – Part I”

What’s in a name

#notetoself.

I’ve used this hashtag as a reminder of things that I’ve found,  I did wrong, lessons I learned by accident or the hard way many times before. So when I thought what would be a good name for a new personal blog, this idea kept coming back to my mind. So there you go… My first tech blog – I had another blog a long time ago, in a galaxy far, far away, when I first came to NZ to keep family and friends informed of my journey to the other side of the world.

What can you expect of this blog? My “notes to self” around the fantastic world of Microsoft Integration. I will try to document things as I learn, gotchas, latest news – whatever I think would be worth coming back later to remind myself. And you.

What I wouldn’t expect if I were you – daily updates, long posts (who am I kidding? If I write like I talk, there will be a chunk of long posts yes), things unrelated to technology (well maybe in rare cases).

So if you made all the way here, thanks, and sit back, relax and enjoy reading as much as I will enjoy writing.

Cheers, Wagner.