Ansible 2.0.0.2 broke compatibility with os-hardening

On a fresh pull and dependencies fetch (including ansible itself) the hardening role was causing ansible to fail to converge due to a [resolved issue](dev-sec/ansible-collection-hardening#64) The requirements file format for ansible-galaxy has been changed to yaml as well to remove a deprecation warning in ansible 2.
iflowfor8hours · Mar 2, 2016 · 730532e · 730532e
1 parent 03640dc
commit 730532e
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -90,7 +90,7 @@ See [test.yml](test.yml)
 
 You can see `test.yml` in action with Vagrant:
 
-* `ansible-galaxy install -r requirements.txt`
+* `ansible-galaxy install -r requirements.yml`
 * `./test/gen-duplicity-keys.sh`
 * `./test/gen-test-cert.sh`
 * Add `test/rootCA.pem` to your browsers trusted authorities list (**note!**

diff --git a/requirements.txt b/requirements.txt
diff --git a/requirements.yml b/requirements.yml
@@ -0,0 +1,13 @@
+- src: jnv.unattended-upgrades
+  version: v1.1.1
+
+- src: geerlingguy.firewall
+  version: 1.0.9
+
+- src: https://github.com/hardening-io/ansible-os-hardening
+  name: hardening.os-hardening
+
+- src: debops.cryptsetup
+  version: v0.2.1
+
+- src: jacksingleton.ramfs