Anton Strogonoff 368ebc8625 fix: Use wait_for_connection to avoid failure (#1381) ... With preexisting wait_for implementation, deployment to Ubuntu on Lightsail failed with a connection reset error on this task. It appears that Ansible’s wait_for_connection is the recommended way. I have successfully gotten past this task after this change, however I’d appreciate more eyes on this.		2019-05-17 16:04:13 +02:00
..
client	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-azure	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-digitalocean	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-ec2	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-gce	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-lightsail	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-openstack	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
cloud-scaleway	Add documentation about Scaleway credentials (#1419)	2019-05-12 11:21:55 +02:00
cloud-vultr/tasks	Automatically create cloud firewall rules for installs onto Vultr (#1400)	2019-04-27 12:59:26 +02:00
common	fix: Use wait_for_connection to avoid failure (#1381)	2019-05-17 16:04:13 +02:00
dns_adblocking	Randomly generated IP address for the local dns resolver (#1429)	2019-05-17 14:49:29 +02:00
dns_encryption	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
local/tasks	WIP: Facts definition fix (#1415)	2019-05-01 11:51:06 +02:00
ssh_tunneling	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
strongswan	Refactoring, Linting and additional tests (#1397)	2019-04-26 11:48:28 -04:00
wireguard	Randomly generated IP address for the local dns resolver (#1429)	2019-05-17 14:49:29 +02:00