Allow more than one instance of this extension on a single VM

[phgogo]

I know that the documentation states...

You can have only one version of an extension applied to the VM. To run a second custom script, you can update the existing extension with a new configuration. Alternatively, you can remove the custom script extension and reapply it with the updated script.

... but i found this behaviour to be extremely inconvenient.

When you work on VMs as a Team, one team member might introduce a custom-script extension doing task A, while another creates one to do task B. They can all life in peace, until they want to deploy them on the same VM.

Un-Installing the first one is not a suitable solution since:

• it make's it harder to debug, since there is no trace of the extension being installed
• Languages like Terraform do not natively support deleting ressources after first provisioning, creating a need for hacky workarounds

Merging to extensions into a single one is painfull as well, if you've been using the "script" parameter in both extensions, which only supports a single script.

I would greatly appreciate it, if this behaviour could be changed! 💛

[MNashDev]

Would also appreciate this! Following

[dhirschfeld]

Would also appreciate this!

Might be an idea to upvote 👍 the request in case they take note of that sort of thing to prioritise requests.

I too find the current behaviour unexpected and extremely inconvenient and would love for multiple extensions to be able to live side-by-side.

I'm in a similar situation to the OP whereby another team pushes an extension by policy onto my machine so I have to wait for their extension to be installed before I can remove it and then add my own. None of that is easy to automate 😬

[jkroepke]

@norakoiralamsft can you look into this somehow?

[meistars]

Meanwhile, its possible to achieve something similar with Managed Run Commands, allows multiple commands and supports ARM templates as well if you wish to deploy it for example with Azure Policy.