Extend StartStopVMs-FA
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
- Domain
- cloud, infrastructure
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/startstopv2-deployments
-
.NET version support Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/startstopv2-deployments#155 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
microsoft/startstopv2-deployments#149 · 2 comments ·
All issues in microsoft/startstopv2-deployments
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
Feature needs-triage pulumi/registry
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
infrastructure launch: scale production
Difficulty 2/5 Half a day Newbie friendliness 72/100
Practitionist/familiarise_web#1772 ·