Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Discussion about Farmer future: Move from ARM templates to AZ CLI

See original GitHub issue

Hello @isaacabraham,

since our morning discussion about how awesome is to have combination of ARM templates with Post-deploy tasks, I am thinking about this:

I love what Farmer can do right now. For example the thing I can setup infrastructure and deploy to it is amazing. The problem here is, that to have both, you need to combine ARM with AZ CLI and as a user of Farmer you have to be aware of it - I need to know that if I’ll only export JSON, my app won’t be deployed.

let myApp = functions {
    name "farmer-amazing-function-app" // <-- ARM
    use_extension_version V3 // <-- ARM
    zip_deploy "path/to/my/app" // <-- AZ CLI

So here it comes. What if we move away from ARM to AZ CLI completely? Yes, you have to have it installed (or supported on CI server), but:

  • You don’t have to know what is part of ARM and what is part of post-deploy task
  • You can support way more features currently not available in ARM
  • You can use well documented AZ CLI instead of terribly semi-documented ARM
  • There is no breaking change in API - library is greatly designed so Builders and their interpretation are totally separated

ARM is about setup of dead infrastructure, but over AZ CLI you can make it alive, which is a kickass feature. I think this would leverage Farmer to completely new level.

What do you think about it? Please take it as trigger for discussion about future and feel free to close immediatelly if you found it completely silly.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

ctolkiencommented, Jul 19, 2020

You don’t have to know what is part of ARM and what is part of post-deploy task

I feel like this could be resolved via making it clearer just via the API? CLI.zip_deploy (pseudocode)

Dzoukrcommented, Jul 17, 2020

Good points (from both of you). I am glad the discussion flows. I like the alternative approach, btw…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Move from ARM templates to AZ CLI #483
Move from ARM templates to AZ CLI #483. isaacabraham started this conversation in Ideas. Move from ARM templates to AZ CLI #483. @isaacabraham...
Read more >
Azure deployment templates with Azure CLI
This article explains how to use Azure CLI with Azure Resource Manager templates (ARM templates) to deploy your resources to Azure.
Read more >
Infrastructure as Code - An intro - Part 4 - Using Bicep
In the last post, I talked about IaC using ARM templates. In this post, I'm looking at ARM templates' “sibling” Bicep.
Read more >
Reasons to use Bicep over Terraform - Marcus Felling
Yes, you can have Terraform deploy an ARM template or use the Azure CLI, but that can get messy stringing it all together,...
Read more >
Azure ARM templates vs AZ CLI : r/devops
Calling all of the Azure DevOps guys; Has anyone transitioned from using ARM templates to AZ CLI with PowerShell?
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found