Skipping Tasks based on Changed
Keep on Learning!
If you liked what you've learned so far, dive in! Subscribe to get access to this tutorial plus video, code and script downloads.
With a Subscription, click any sentence in the script to jump to that part of the video!
Login SubscribeThanks to the when key, you can make your playbooks really really smart and really really fast. What else could we do? Well, sometimes, our code doesn't change. When that happens, the "Checkout Git repository" will report as "ok", so not Changed.
If we know that the code didn't change... then it might not make sense to install our composer dependencies. After all, if the code didn't change, how would the composer dependencies need to change? And we could skip other things, like running the migration or even clearing the cache.
Under the "Git" task, register a new variable: repo_code:
| - hosts: vb | |
| // ... lines 3 - 26 | |
| tasks: | |
| // ... lines 28 - 138 | |
| - name: Checkout Git repository | |
| // ... lines 140 - 143 | |
| register: repo_code | |
| // ... lines 145 - 248 |
We already know from the output that we're looking for the changed key on this variable. That means, we could use repo_code.changed in the when option of some tasks to skip them.
Using set_fact to Clean Variables
But, we can get fancier! Below this task, add a new one called "Register code_changed variable". We'll use the set_fact module from earlier. This time, create a new variable called code_changed set to, very simply, repo_code.changed:
| - hosts: vb | |
| // ... lines 3 - 26 | |
| tasks: | |
| // ... lines 28 - 138 | |
| - name: Checkout Git repository | |
| // ... lines 140 - 143 | |
| register: repo_code | |
| // ... lines 145 - 147 | |
| - name: Register code_changed variable | |
| set_fact: | |
| code_changed: repo_code.changed | |
| // ... lines 151 - 250 |
The only reason we're doing this is to make our when statements a little cleaner. Add our tag onto that.
Down below, under "Install Composer's Dependencies", add when: code_changed:
| - hosts: vb | |
| // ... lines 3 - 26 | |
| tasks: | |
| // ... lines 28 - 188 | |
| - name: Install Composer's dependencies | |
| // ... lines 190 - 194 | |
| when: code_changed | |
| // ... lines 196 - 250 |
Tip
Ansible does not allow evaluating bare variables anymore. The code_changed variable is not
obviously a boolean value because it just references to another variable called repo_code.changed,
so Ansible requires the |bool filter to be added to the code_changed in when clauses:
# ansible/playbook.yml
---
- hosts: vb
# ...
tasks:
# ...
- name: Install Composer's dependencies
# ...
when: code_changed | boolAh, so nice. Copy that and put it anywhere else it makes sense like "Execute migrations" and "Clear Cache":
| - hosts: vb | |
| // ... lines 3 - 26 | |
| tasks: | |
| // ... lines 28 - 215 | |
| - name: Execute migrations | |
| // ... lines 217 - 221 | |
| when: code_changed | |
| // ... lines 223 - 230 | |
| - name: Clear cache | |
| // ... lines 232 - 235 | |
| when: code_changed | |
| // ... lines 237 - 250 |
Phew! Ok, run the playbook - but take off the verbose flag:
ansible-playbook ansible/playbook.yml -i ansible/hosts.ini -t deploy
As cool as this is, you need to be careful. As you make your playbook smarter, it's also more and more possible that you introduce a bug: you skip a task when it should actually run. I've just made a small mistake... which we'll discover soon.
But for now, it's so cool: the 3 Composer tasks were skipped, as well as installing Composer's dependencies, migrations and the "Clear Cache". And thanks to that, the playbook ran way faster than before.
It's time to talk about getting our playbook a bit more organized. As you can see... it's getting big... and I'm getting a bit lost in it. Fortunately, we have a few good ways to fix this.
Hello,
My first message on the platform!
Thank you very much for the quality of your tutorials.
Despite my poor English proficiency, I can follow the courses.
Ansible does notice: [DEPRECATION WARNING]: evaluating repo_code.changed as a bare variable.
To solve this notification, just add a pipe bool (|bool) like this :
when: code_changed|boolCheers!