Azure provider do not support user_data

[stonevil]

Azure provider do not support user_data. I cannot automatically deploy CoreOS cluster at Azure without this options.

[stonevil]

Ok. I can do almost this same with provision file and remote-exec

[stonevil]

It cannot do this same with provision file and remote-exec.

Please add support for user_data (custom_data for Azure)

[mtekel]

+1

[saliceti]

definitely +1

[keymon]

+1

[aznashwan]

@everyone: sadly; at the time of the writing of the Azure provider for Terraform; the go sdk was based on the old ASM API's which made sending userdata difficult. As a result; even nowadays the go sdk does not support instance user_data over the old ASM API's.

The addition of the new ARM API's should lead to the enablement of all these problems though.
For updates on the status of the transition; please refer to #3212

[skevy]

@aznashwan It seems like it IS possible to do user data with the current SDK:

https://github.com/Azure/azure-sdk-for-go/blob/1a29bf058b780f6a05fc67111efae7930c4a1621/management/virtualmachine/entities.go#L349

I know you guys are moving to ARM from ASM, but this would be a relatively easy fix if we do something a bit custom here: https://github.com/hashicorp/terraform/blob/master/builtin/providers/azure/resource_azure_instance.go#L283, instead of relying on their helper (which doesn't take custom data).

Would you accept a PR for this as a stop gap solution? Not having custom data on azure really limits it's use case for me (and I presume many others).

[stack72]

Closed via #8158

[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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.