Add support for shutdown or start VM

[ggjulio]

Community Guidelines

• [X] I have read and agree to the HashiCorp Community Guidelines .
• [X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• [X] Do not leave "+1" or other comments that do not add relevant information or questions.
• [ ] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

See the description of closed issue #1394.

However unlike the proposal of #1394. I think creating a new resource vsphere_virtual_machine_state would be more appropriate than adding a new key desired_status to vsphere_virtual_machine. It won't blur the lines between mutable vs. immutable infrastructure.

Example 1:

resource "vsphere_virtual_machine_state" "main" {
  uuid  = vsphere_virtual_machine_state.main.uuid
  state = data.coder_workspace.me.transition == "start" ? "running" : "stopped"
}

Example 2:

resource "vsphere_virtual_machine_state" "main" {
  name           = vsphere_virtual_machine_state.main.name
  datacenter_id  = data.vsphere_datacenter.datacenter.id
  state          = data.coder_workspace.me.transition == "start" ? "running" : "stopped"
}

Use Case(s)

Provide ability to start and stop a virtual machine from terraform. Feature parity with providers such as AWS

example Source: https://registry.coder.com/templates/aws-linux

Potential Terraform Provider Configuration

No response

References

1394 #1533 #1394

[github-actions[bot]]

Hello, ggjulio! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.