Extend StartStopVMs-FA

Open
#108 0 comments 0 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

Research direction

Start by locating the StartStopVMs function and its existing scheduling and subscription-handling entry points. Clarify how stopped versus deallocated VMs, resource groups, multiple subscriptions, and the morning schedule should be handled. Done should mean the requested VMs are identified and started according to the agreed scope.

Written by the indexing model from the issue text.

Description

Dear Author,

Could we extend the StartStopVMs function. Our requirement is to first _check VMs for 'stopped' / 'deallocated' status in the various resource groups within multiple subscriptions and accordingly start them every morning at a particular time.

Best regards

Preetam

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.