-
Notifications
You must be signed in to change notification settings - Fork 452
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
feat: add support for applying existing customization specs #2053
feat: add support for applying existing customization specs #2053
Conversation
4bc9d9f
to
ee61b3a
Compare
vsphere/internal/vmworkflow/virtual_machine_clone_subresource.go
Outdated
Show resolved
Hide resolved
vsphere/internal/vmworkflow/virtual_machine_clone_subresource.go
Outdated
Show resolved
Hide resolved
vsphere/internal/vmworkflow/virtual_machine_clone_subresource.go
Outdated
Show resolved
Hide resolved
vsphere/internal/vmworkflow/virtual_machine_clone_subresource.go
Outdated
Show resolved
Hide resolved
vsphere/internal/vmworkflow/virtual_machine_clone_subresource.go
Outdated
Show resolved
Hide resolved
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.
- Added suggestions for error and log messages.
- Added suggestions for descriptions.
- Noted a missing description.
- Noted
type
is required.
Otherwise, this looks great!!! If you can make these changes I'll test tomorrow.
830421a
to
f57cff9
Compare
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.
Two open suggestion and merge conflicts need to be resolved.
…pecs to r/virtual_machine - added `vsphere_guest_os_customization` data source for existing customization specs - added `vsphere_guest_os_customization` resource for CRUD operations on customization specs - added customization_spec attribute to VirtualMachineCloneSchema to enable `vsphere_guest_os_customization` usage on VM clone - virtual machine customization and guest os customization are using the same code for expanding/flattening specs sent to API - deleted the file containing the common code regarding guest OS customizations shared between VM and customizations - created e2e tests - added documentation for `d/vsphere_guest_os_customization` and `r/vsphere_guest_os_customization` - addressed comments Testing done: - `make build` - Verified that the folowing e2e tests pass: - TestAccResourceVSphereVirtualMachine_cloneWithDifferentHostname - TestAccResourceVSphereVirtualMachine_cloneCustomizeWithNewResourcePool - TestAccResourceVSphereVirtualMachine_cloneWithDifferentTimezone - TestAccResourceVSphereVirtualMachine_cloneCustomizeForceNewWithDatastore - Verified that the newly introduced e2e tests pass Signed-off-by: Vasil Atanasov <[email protected]>
f57cff9
to
a92a5b5
Compare
I've rebased and resolved the conflicts. |
7d56a37
to
5792d76
Compare
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.
LGTM! 🚀
Wonderful work, Vasil!
5792d76
to
3227efa
Compare
3227efa
to
b0ed0b7
Compare
b0ed0b7
to
5e215a5
Compare
…pecs to r/virtual_machine - added `vsphere_guest_os_customization` data source for existing customization specs - added `vsphere_guest_os_customization` resource for CRUD operations on customization specs - added customization_spec attribute to VirtualMachineCloneSchema to enable `vsphere_guest_os_customization` usage on VM clone - virtual machine customization and guest os customization are using the same code for expanding/flattening specs sent to API - deleted the file containing the common code regarding guest OS customizations shared between VM and customizations - created e2e tests - added documentation for `d/vsphere_guest_os_customization` and `r/vsphere_guest_os_customization` - addressed comments Testing done: - `make build` - Verified that the folowing e2e tests pass: - TestAccResourceVSphereVirtualMachine_cloneWithDifferentHostname - TestAccResourceVSphereVirtualMachine_cloneCustomizeWithNewResourcePool - TestAccResourceVSphereVirtualMachine_cloneWithDifferentTimezone - TestAccResourceVSphereVirtualMachine_cloneCustomizeForceNewWithDatastore - Verified that the newly introduced e2e tests pass Signed-off-by: Vasil Atanasov <[email protected]>
5e215a5
to
903db0a
Compare
This functionality has been released in v2.6.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! |
1 similar comment
This functionality has been released in v2.6.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 issues. 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. |
Testing done:
make build
Verified that the folowing e2e tests pass:
Verified that the newly introduced e2e tests pass
Description
vsphere_guest_os_customization
data source for existing customization specsvsphere_guest_os_customization
resource for CRUD operations on customization specsvsphere_guest_os_customization
usage on VM cloned/vsphere_guest_os_customization
andr/vsphere_guest_os_customization
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Closes #1604