[ASK] Does VM start/stop V2 solution support adding new Logic App and use user-assigned MI instead?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud
Research direction
Start with the linked scheduled start-and-stop deployment documentation and inspect the existing Logic App and Function App configuration. Determine whether separate Logic Apps can trigger the Function App with different schedules and whether a user-assigned managed identity is supported; document the supported configuration or the required implementation scope.
Written by the indexing model from the issue text.
Description
There are two questions about VM start/stop V2 solution. Very appreciate that if someone has insights on it.
We're trying to customize the VM start/stop V2 solution by below two requirements.
-
Use VM start/stop V2 solution to start/stop the VMs in multiple subscriptions but with different schedules, however we do not see the option to add multiple schedules in the logic app created among with this solution. Can a new logic app be integrated with this solution to be triggered by the same Function app?
-
Use of user assigned managed identity instead of the system assigned identity for function app
Assessment from my view:
Cosulting with Logic App, the Logic App (non-standard) only support one workflow one Recurrence (scheduler), you could view it from Logic app designer. Hence, if multiple schedulers are required, we need to create a separated new Logic App for each scheduler.
But I’m not sure about if it’s supported to add new Logic App into existing Start/Stop VMs v2 solution to trigger existing Function App and whether it’s supported to use User-assigned managed identity to replace the default system-assigned managed identity.
I found the workaround is to configure request body to assign multiple subscriptions to manage VMs across different subscriptions in the Logic App. But we still preferred to use different schedules (different Logic Apps) to manage VMs across multiple subscriptions.
- Dominant language
- No language data
- Stars
- 58
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 supportOpen
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 84/100
nasa/cumulus-process-py#156 ·
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pnp/pnpcore#1878 · 1 comment ·
Maintainers usually reply within 1 day
-
render.yamlOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
[BUG] `RunsArtifactRepository.download_artifacts` reports artifact store errors as a wrong pathOpenarea/tracking
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:deploy prio:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day