Feature Request: Add support to control VMSS instances in start/stop operation

Open
#86 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
cloud, infrastructure

Research direction

Start by reviewing the existing start/stop handling and the invalid ARM URI shown in the issue. Define the required VMSS instance behavior and validation, then confirm that start and stop requests work for the reported virtualMachineScaleSets resource path.

Written by the indexing model from the issue text.

Description

As titled, one of my clients would like to implement the start/stop from VMSS, and encountered the below error:

{

  "successful": false,

  "message": "Encountered a request scope with an invalid value. The provided resource ARM URI /subscriptions/xxxx/resourceGroups/xxxx/providers/Microsoft.Compute/virtualMachineScaleSets/xxxx/virtualMachines/xx is invalid. 
  Uri should contain a provider of type /providers/Microsoft.Compute/virtualMachines or /providers/Microsoft.ClassicCompute/virtualMachines."
}

I understand it may be a by-design scenario, but is it fine if we can add the VMSS support in the later backlog?

Dominant language
No language data
Stars
58
Forks
35
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.