Tag-based schedules
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
Research direction
Start by reviewing the linked Azure Automation scenario and issue 96207 to understand the requested tag-based scheduling behavior. Then inspect the repository's deployment entry points and define the supported tag format, schedule handling, and multi-subscription behavior. Done means teams can manage VM start/stop schedules through tag values without per-VM PRs or separate deployments.
Written by the indexing model from the issue text.
Description
Please add the ability to perform scheduled start/stop based on tag values.
In a large organisation with many subscriptions managed by many teams, there are many different schedules.
The 3 options I see are:
- Those teams would need to constantly message the start/stop team
- They would need to be able to submit PRs to add their individual VMs to the appropriate schedule
- We need to deploy many copies of this so individual teams can manage their own
Here is a great example of doing this with a json tag: Azure Automation scenario - using JSON formatted tags to create a schedule for Azure VM startup and shutdown
Here is another example of the same request: 96207
- 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 ·