Stop all VM in subscription

Open
#102 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure
Domain
cloud

Research direction

Start with the stop function's handling of RequestScopes and compare how ResourceGroups, Subscriptions, and VMLists are applied. Reproduce the configuration shown in the issue and trace why test-2 is included; done means the stop action affects only the requested test-interni VM.

Written by the indexing model from the issue text.

Description

Hello I setup the stop to try the function but when i set the rg and vmlist it tries always to stop the vm in the subscription

the definition in the stop function call

{ "Action": "stop", "EnableClassic": false, "RequestScopes": { "ResourceGroups": [ "/subscriptions/XXXXXX/resourceGroups/test/" ], "Subscriptions": [ "/subscriptions/XXXXXX/" ], "VMLists": [ "/subscriptions/XXXXXX/resourceGroups/test/providers/Microsoft.Compute/virtualMachines/test-interni" ] } }

this the output i get when i run the function

{
"successful": true,
"message": "~Scheduled: Attempted the stop action on the following ARM VMs: test-2, test-interni"
}

test-2 vm is on another rg

What I made wrong?

Dominant language
No language data
Stars
58
Forks
35
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/startstopv2-deployments

All issues in microsoft/startstopv2-deployments

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.