question-mark
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.

[App Service] [Discussion] Shorten appservice command group name to just "app"

See original GitHub issue

I’d love to discuss whether we could shorten the appservice command group to just app (or equivalent) in order to improve the ergonomics around frequent use. The use of az instead of “Azure” feels so fluid to type (as does nsg, vm, nic, acs, acr, etc.), and I wonder whether we couldn’t apply a similar naming abbreviation “principal” for App Service, in order to improve the efficiency of using its command on a regular basis, while balancing intuitiveness/discoverability.

Personally, I don’t find the use of <TAB> for auto-completing long command names to be very ergonomic, which is why I’ve thrown out the possibility of shortening names vs. relying on tab completion. Others may find this acceptable, so I’m just providing one input, which may not be that useful. Apologies if this conversation has already happened. I just wanted to throw it out there while the App Service module was still in beta, and could potentially make a breaking change like this.

UPDATE: As discussed below, an alternative solution to this could be to “flatten” out the appservice command group and provide top-level support for web apps itself (e.g. az webapp). I personally prefer this solution, and would support it over the above previous proposal

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:14 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
yugangw-msftcommented, May 9, 2017

We went with webapp

1reaction
stewartadamcommented, Mar 20, 2017

Note that the portal also further distinguishes between bot, API, web, etc apps as well. A decision to use top-level namespaces will need to be clear on how to brand these types of apps (if it is going to at all), and if so then any new possible new classes of apps going forward.

imho, a single top-level group like @tjprescott described is best and provides the most flexibility going onward. Understood that there are other pressures for naming, my 0.02 is we should do what makes the most sense for the CLI tooling to make sure it’s consistent and easy to use. As it stands, Logic Apps are branded underneath App Service: https://azure.microsoft.com/en-us/services/logic-apps/

Read more comments on GitHub >

github_iconTop Results From Across the Web

7 Tips and Tricks for Azure App Service | Microsoft Learn
To begin, go to the Azure Portal and select an App Service that you've ... To navigate or type in a command, just...
Read more >
[App Service] Getting Started ("North Star") · Issue #19 - GitHub
The goal of App Service should be to enable developers to get up and ... the config appsettings command group to simply env...
Read more >
How To Clone An Azure Web App? - Parveen Singh
Fill out the name for new web application and pick a resource group where you'd like to deploy it. You have the option...
Read more >
Azure app service plan - Pragim Tech
In our previous video we discussed what is App Service. ... this plan for our web application PragimTech.com, so it makes sense to...
Read more >
Azure App Service Plan - Specify App Size with PowerShell
The PowerShell command for this is confusing for two reasons: The docs are missing the property you need for this, "WorkerSize" ...
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 Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found