You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Marking this issue as stale due to inactivity in the past 180 days. This helps us focus on the active issues. If this issue is reproducible with the latest version of the provider, please comment. 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!
Community Guidelines
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 keydesired_status
tovsphere_virtual_machine
.It won't blur the lines between mutable vs. immutable infrastructure.
Example 1:
Example 2:
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
The text was updated successfully, but these errors were encountered: