-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compute
: Add user_data
to VM & VMSS resources
#13888
Conversation
ba4ca50
to
3e34fa3
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Mathieu Ouellet <[email protected]>
Signed-off-by: Mathieu Ouellet <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey @mouellet
Thanks for this PR - apologies for the delay reviewing this.
I've taken a look through and left some comments inline - since the design of Custom Data within a Virtual Machine and Virtual Machine Scale Sets has quite a unique behaviour, in order to review this PR I ended up having to pull this down locally to confirm if this also applies to User Data.
For context, the issue with Custom Data is that this also a Base64 encoded string available at provisioning time - however this isn't returned from the Azure API (which is why in the acceptance tests we're ignoring the value of this field). Having looked into this, this value is returned for this field (which makes sense as this is available via the Instance MetaData Endpoint) so we're good here (and can ensure this is set into the state / remove the ignore
checks for this field).
As I mentioned since I've pulled this down locally and some left comments inline, so I hope you don't mind but I'm going to push a few commits to resolve the outstanding comments - but as this otherwise looks good to me I'll kick off the acceptance tests now and we should be able to get this merged shortly 👍
Thanks!
internal/services/compute/windows_virtual_machine_scale_set_resource_test.go
Outdated
Show resolved
Hide resolved
internal/services/compute/windows_virtual_machine_resource_test.go
Outdated
Show resolved
Hide resolved
internal/services/compute/linux_virtual_machine_scale_set_resource_test.go
Outdated
Show resolved
Hide resolved
internal/services/compute/linux_virtual_machine_scale_set_resource.go
Outdated
Show resolved
Hide resolved
internal/services/compute/windows_virtual_machine_scale_set_other_resource_test.go
Outdated
Show resolved
Hide resolved
internal/services/compute/windows_virtual_machine_scale_set_other_resource_test.go
Outdated
Show resolved
Hide resolved
test failure:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks LGTM 🍰
This functionality has been released in v2.91.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! |
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. |
Fix for #11846