#41 Rename aws and vagrant scenario's molecule yamls, since EC2 and V…

…agrant are currently unsupported by Molecule V3 - see ansible/molecule#2560
jonashackt · Feb 24, 2020 · 861c1ba · 861c1ba
1 parent eb2c795
commit 861c1ba
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/Pipfile b/Pipfile
@@ -8,7 +8,7 @@ verify_ssl = true
 [packages]
 ansible = "==2.9.5"
 molecule = "==3.0.2"
-testinfra = "==3.4.0"
+testinfra = "==4.1.0"
 python-vagrant = "==0.5.15"
 awscli = "==1.16.313"
 boto = "==2.49.0"

diff --git a/Pipfile.lock b/Pipfile.lock
diff --git a/docker/molecule/aws-ec2-ubuntu/molecule.yml → docker/molecule/aws-ec2-ubuntu/molecule0.yml b/docker/molecule/aws-ec2-ubuntu/molecule.yml → docker/molecule/aws-ec2-ubuntu/molecule0.yml
diff --git a/docker/molecule/vagrant-ubuntu/molecule.yml → docker/molecule/vagrant-ubuntu/molecule0.yml b/docker/molecule/vagrant-ubuntu/molecule.yml → docker/molecule/vagrant-ubuntu/molecule0.yml