LinuxConfiguration Support in Compute Resource Provider

[danielsollondon]

In the CRP API version 2018-06-01 we added support for :
"linuxConfiguration": {
"provisionVMAgent": false
}

This is not available in azurerm_virtual_machine in os_profile_linux_config.

Can you advise when this can be made available?

Thanks,

[danielsollondon]

what is the rough ETA for 2.0.0?

[tombuildsstuff]

@danielsollondon we're still trying to scope it to determine roughly what should be in 2.0 - so there's timeline at this point - but a rough gues-timate would be early next year.

Whilst it'd be possible for someone to include this in the azurerm_virtual_machine resource before then (and we're happy to accept a PR for this in the interim, it'd need to include a state migration but we can assist/guide this) - we're looking at splitting the VM and VMSS resources into 2 resources for each (a Linux/Windows VM and a Linux/Windows VMSS resource). As such I believe 2.0 would be the best time to add support for this new field since we'll be reevaluating these resources anyway.

Thanks!

[tombuildsstuff]

hey @danielsollondon

Apologies for the delayed update here!

Over the past few months we've been working on the functionality coming in version 2.0 of the Azure Provider (outlined in #2807). We've just released version 1.43 of the Azure Provider which allows you to opt-in to the Beta of these upcoming features, including the new azurerm_linux_virtual_machine resource which supports configuring provision_vm_agent.

Unfortunately there's no plans to backport this to the existing azurerm_virtual_machine resource - however the new azurerm_linux_virtual_machine resource will go GA in version 2.0 of the Azure Provider in the coming weeks.

Since this functionality is available in the new azurerm_linux_virtual_machine resource (which can be used by opting into the beta) I'm going to close this issue for the moment - but please let us know if that doesn't work for you and we'll take another look.

Thanks!

[ghost]

This has been released in version 2.0.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.0.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!