Azure / Azure/azure-quickstart-templates
multiple CustomScript Vm Extensions on same vm error
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
I have seen simiar issues like this form 2015 etc but i am wondering if this feature is still not supported or if there is some special way to do this?
I cannot merge the two extension scripts because one needs to happen first, then another machine deploys and afterwards the second extension script can run
### Issue Details
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"Multiple VMExtensions per handler not supported for OS type 'Windows'. VMExtension 'ImportGPO' with handler 'Microsoft.Powershell.DSC' already added or specified in input.\"\r\n }\r\n}"}]}
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository file or test. Start by checking Azure VM extension deployment behavior for multiple CustomScript and DSC handlers, using the reported deployment error as the entry point; done would require a confirmed supported configuration or a clearly scoped template or documentation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100