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.

az vm stop in the CLI stops the VM but Stop in the portal deallocates the resources. need parity between the two?

See original GitHub issue

Description

Outline the issue here:

az vm stop in the CLI stops the VM but does not deallocate the resources. The customer continues to get charged for the resources. Stop in the portal though deallocates the resources. I think we should have parity between the 2.

Environment summary

Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:pip

CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:dev build

OS Version: What OS and version are you using?
Answer here:MACOS

Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here:terminal

Issue Analytics

State:
Created 6 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

4reactions

jlukcommented, Sep 13, 2017

@sauryadas there is the cmd az vm deallocate to mimic the portal version of “stop”. It seems CLI properly has 2 separate commands appropriately named and portal is overloading the term “stop” incorrectly.

I think we should get Vlad to update buttons for “stop” and “stop-deallocate”.

0reactions

adewaleocommented, Jan 2, 2019

The help for the CLI was updated as part of the merged PR above. The changes in that PR will be reflected in the next release of the CLI (January 15). The online documentation will be updated around the release as well.