[Feature]: hcloud server (start_after_create)

[cloudfy]

What whould you like to see?

When creating a hcloud server, ability to se start_after_create true/false

[jansedlon]

Second this. Right now the servers are created turned off

[jooola]

Second this. Right now the servers are created turned off

This should not be the case, you might be running into a bug. Please open a ticket using the Support Center.

[apricote]

Hey @cloudfy and @jansedlon,

can you explain your use-case for creating turned-off servers in Terraform? This feels at-odds with the declarative approach terraform enforces, so I am curious to hear how you would like to use this.

[cloudfy]

Ensuring subnet allocation without having to specify fixed IP address. The way Hetzner made the allocation of network, I cannot assign subnet to a server, ensuring the proper IP when it boots. The use-case is to create server stopped, remove from network, assign to subnet and then start, which boots the server with the right ip.

[apricote]

The API now supports attaching directly to a subnet. We added support for it in #1217 for the hcloud_server_network resource, but it is missing in hcloud_server. Would that solve your requirement?

Is it necessary that the server only boots when it's assigned to the right private network + subnet?

[cloudfy]

Is it necessary that the server only boots when it's assigned to the right private network + subnet?
Proper cloud_init in scalable designs require the subnet to be correct.

I echo the #1217 , "Using the subnet_id argument is preferred over the network_id argument."

Small deployment is fair to use a small network_id, but when it comes to scalable subnets, the subnet is most important. In such case, assigning the subnet to a "stopped" server can be voided, rendering the parameter suggestion (start_after_create) obsolute.

[mlinares1998]

The API now supports attaching directly to a subnet. We added support for it in #1217 for the hcloud_server_network resource, but it is missing in hcloud_server. Would that solve your requirement?

Is it necessary that the server only boots when it's assigned to the right private network + subnet?

Hi @apricote, @jooola, @cloudfy

I've opened #1265, which seems related to this issue as well.

I need to create VMs directly in a target subnet with only a private IP (no public IP). Having subnet_id support in hcloud_server would be ideal for this scenario.

As described in #1265, chaining hcloud_server + hcloud_server_network with a single private interface fails, because the server attempts to boot before the hcloud_server_network resource is applied. This causes hcloud_server creation failures since there's no interface available at boot time.

Would adding subnet_id support directly to hcloud_server be something you'd consider?
Thanks!