Wrench down retries to try to get sanity back

ansible.cfg

@@ -1,14 +1,12 @@
 [defaults]
-# I have a large number of machines, which warrants a large forks setting
-# here.
-forks = 16
+# Tune this higher if you have a large number of machines
+forks = 8
 # We set gathering to smart here as I'm often executing the site-wide playbook,
 # which means a ton of redundant time gathering facts that haven't changed
 # otherwise.
 gathering = smart
 # host_key_checking is disabled because nearly 90% of my Ansible plays are in
 # ephemeral environments and I'm constantly spinning machines up and down.
-# In theory this is an attack vector that I need to work on a solution for.
 host_key_checking = false
 # Explicitly set the python3 interpreter for legacy hosts.
 interpreter_python = python3
@@ -28,7 +26,7 @@ roles_path = .roles:roles
 system_warnings = true
 # We set this to avoid circumstances in which we time out waiting for a privesc
 # prompt. Zerotier, as a management network, can be a bit slow at times.
-timeout = 60
+#timeout = 30
 # Bad
 vault_password_file = ~/.vault_pass
 
@@ -41,9 +39,8 @@ always = true
 become = true
 
 [ssh_connection]
-# The number of retries here is insane because of the volatility of my home
-# network, where a number of my machines live.
-retries = 15
+# We set retries to be a fairly higher number, all things considered.
+#retries = 3
 # These extra args are used for bastioning, where the ephemeral Ansible
 # controller remotes into a bastion machine to access the rest of the
 # environment.