[Bug]: Inconsistency between server gui and terraform provider

[hadmut]

What happened?

I did not understand it

What did you expect to happen?

I hope to understand it.

Please provide a minimal working example

When using the Hetzner Cloud Web GUI, it says, that servers can never be attached to a network, once a network has more than one subnet. Once more than a subnet is defined, it tells to add the server to one of the subnets.

https://console.hetzner.cloud/projects/.../networks/.../resources

In contrast, https://registry.terraform.io/providers/hetznercloud/hcloud/latest/docs/resources/server_network tells that hosts can be added to either the network or a subnet without any restriction.

Just a detail, but it does not seem to be consistent and might cause problems if the Hetzner Cloud and the terraform provider behave differently.

[hadmut]

Yeah.

When trying to add a server to a network without having subnets, it produces an error message

Error: attach server to network: no subnet or IP available (no_subnet_available, ...)

If that's intended, there should be some clarification in the docs of the terraform provider, that a matching subnet has to exist.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.