hetzner.hcloud.hcloud_network module is missing network_zone option about hetzner.hcloud HOT 4 CLOSED

To define the network zone, you should probably use the subnetwork module: https://docs.ansible.com/ansible/latest/collections/hetzner/hcloud/hcloud_subnetwork_module.html#parameter-network_zone

from hetzner.hcloud.

@jooola We're talking about a network, not a subnetwork. Lookup the hetzner cloud: When you create a network, eu-central is automatically assigned. There is no need to create another subnetwork:

Please re-open the request.

from hetzner.hcloud.

When creating a network on the console, a subnet is automatically added to the network after its creation. If you delete all the subnets in the network, you will be able to create a new subnetwork and define the network zone:

If you look at the API reference https://docs.hetzner.cloud/#networks-create-a-network, you can see that the subnetworks are holding the network zone information.

So you have to do the following:

- name: Create a network
  hetzner.hcloud.hcloud_network:
    name: my-network
    ip_range: 10.0.0.0/8
    state: present

- name: Create a subnetwork
  hetzner.hcloud.hcloud_subnetwork:
    network: my-network
    ip_range: 10.0.0.0/16
    network_zone: eu-central
    type: cloud
    state: present

from hetzner.hcloud.

OK, thank you for clarifying. 👍

from hetzner.hcloud.