azurerm_orchestrated_virtual_machine_scale_set - support for the user_data_base64 property

[gcampbell12]

Adds user data to VMSS azurerm_orchestrated_virtual_machine_scale_set resource, the VMSS API requires this value to be base64 encoded hence the schema validation

[gcampbell12]

Acceptance test results:

==> Checking that code complies with gofmt requirements...
==> Checking that Custom Timeouts are used...
==> Checking that acceptance test packages are used...
TF_ACC=1 go test -v ./internal/services/compute -run=TestAccOrchestratedVirtualMachineScaleSet_otherUserData -timeout 60m -ldflags="-X=github.com/hashicorp/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN   TestAccOrchestratedVirtualMachineScaleSet_otherUserData
=== PAUSE TestAccOrchestratedVirtualMachineScaleSet_otherUserData
=== CONT  TestAccOrchestratedVirtualMachineScaleSet_otherUserData
--- PASS: TestAccOrchestratedVirtualMachineScaleSet_otherUserData (460.98s)
PASS
ok      github.com/hashicorp/terraform-provider-azurerm/internal/services/compute       462.354s

[katbyte]

Thanks @gcampbell12, this LGTM thou i wonder if we should be explicit in what the property expects and call it user_data_base64 as we often put json etc on the end to make it clear

[katbyte]

Thanks @gcampbell12 - LGTM now ⚙️

[github-actions]

This functionality has been released in v3.24.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.