Changing `vra_network` for a `vra_machine` resource results in no changes

[PaulAngus]

Code of Conduct

This project has a Code of Conduct that all participants are expected to understand and follow:

• [ x ] I have read and agree to the project's Code of Conduct

vRA Version

8.16.1

Terraform Version

1.7.0

vRA Terraform Provider Version

0.9.0

Affected Resource(s)

vra_machine

Terraform Configuration Files

data "vra_network" "network" {
  name = var.vmnetworkname
}

resource "vra_machine" "vm" {
  name          = var.vmname
  flavor        = var.vmflavorname
  image         = var.vmimagename
  project_id    = data.vra_project.project.id

  nics {
    network_id = data.vra_network.network.id
}

Expected Behavior

Changing the vra_network that a vra_machine is connected to and re-running terraform apply should change the network which the machine is connected.

Actual Behavior

Terraform immediately returns that the modifications are complete. However, no changes have been made. It does not appear that any attempt is made to make this change.

Steps to Reproduce

Create a deployment with the a vra_machine connected to a network, change the network the vra_machine should be connected to, and re-run terraform apply.

Screenshots

Debug Output

Panic Output

Important Factoids

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[frodenas]

Updating the network interfaces for a machine is a feature that is currently not supported. We should at least document this gap in the resource documentation and/or emit a warning message when updating the resource.

[github-actions]

Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!

[github-actions]

Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!