use resource-level connection blocks...

this is now possible, since all our provisioners are using
the same settings. And it saves a bunch of lines

servers.tf

@@ -15,31 +15,24 @@ resource "hcloud_server" "control_planes" {
     "engine"      = "k3s",
   }
 
+  connection {
+    user           = "root"
+    private_key    = local.ssh_private_key
+    agent_identity = local.ssh_identity
+    host           = self.ipv4_address
+  }
+
   provisioner "file" {
     content = templatefile("${path.module}/templates/config.ign.tpl", {
       name           = self.name
       ssh_public_key = local.ssh_public_key
     })
     destination = "/root/config.ign"
-
-    connection {
-      user           = "root"
-      private_key    = local.ssh_private_key
-      agent_identity = local.ssh_identity
-      host           = self.ipv4_address
-    }
   }
 
   # Install MicroOS
   provisioner "remote-exec" {
     inline = local.MicroOS_install_commands
-
-    connection {
-      user           = "root"
-      private_key    = local.ssh_private_key
-      agent_identity = local.ssh_identity
-      host           = self.ipv4_address
-    }
   }
 
   # Issue a reboot command
@@ -75,13 +68,6 @@ resource "hcloud_server" "control_planes" {
       node-taint               = var.allow_scheduling_on_control_plane ? [] : ["node-role.kubernetes.io/master:NoSchedule"]
     })
     destination = "/etc/rancher/k3s/config.yaml"
-
-    connection {
-      user           = "root"
-      private_key    = local.ssh_private_key
-      agent_identity = local.ssh_identity
-      host           = self.ipv4_address
-    }
   }
 
   # Run an other control plane server
@@ -102,13 +88,6 @@ resource "hcloud_server" "control_planes" {
         done
       EOT
     ]
-
-    connection {
-      user           = "root"
-      private_key    = local.ssh_private_key
-      agent_identity = local.ssh_identity
-      host           = self.ipv4_address
-    }
   }
 
   network {