iterm: hoist variables up to top level

In 50256f3 I said that I didn't like the implicit dependency of the "dotfiles" role on the "iterm" role (for the purposes of getting these variables). Just got bitten by it (I had run the "dotfiles" role and forgotten to run the "iterm" role beforehand), so moving the variables up into the top level, lest this happen again.
wincent · Mar 29, 2018 · f3bdb94 · f3bdb94
1 parent f4b0666
commit f3bdb94
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 14 deletions.
diff --git a/group_vars/all.yml b/group_vars/all.yml
@@ -3,5 +3,13 @@ corpus_notes: "{{ '~/Documents/Corpus' | expanduser }}"
 git_cipher_path: vendor/git-cipher/bin/git-cipher
 http_proxy: ""
 iterm_dynamic_profiles:
-  external: []
-  retina: []
+  external:
+    - dest: Mutt.json
+      src: 40-Mutt-4K.json
+    - dest: Wincent.json
+      src: 10-4K.json
+  retina:
+    - dest: Mutt.json
+      src: 40-Mutt-Retina.json
+    - dest: Wincent.json
+      src: 10-Retina.json
diff --git a/roles/iterm/defaults/main.yml b/roles/iterm/defaults/main.yml