.drone.yml

@@ -39,7 +39,7 @@ steps:
       NPM_CONFIG_LOGLEVEL: error
 
   - name: testbuild
-    image: thegeeklab/hugo:0.93.2
+    image: thegeeklab/hugo:0.97.3
     commands:
       - hugo --panicOnWarning -b http://localhost/
 
@@ -51,7 +51,7 @@ steps:
       LINK_VALIDATOR_BASE_DIR: public/
 
   - name: build
-    image: thegeeklab/hugo:0.93.2
+    image: thegeeklab/hugo:0.97.3
     commands:
       - hugo --panicOnWarning
 
@@ -127,6 +127,6 @@ depends_on:
 
 ---
 kind: signature
-hmac: 1c32b1665bc82ba2e1f954d477245f96f36daf2970cd76ffd993b82be0d9062a
+hmac: 7236d10a29eff08ad942b33273f572a254ce17c42d316a336f8c3a15398b78f4
 
 ...

content/posts/2020/ansible-and-the-relations-to-the-inventory/index.md

@@ -24,7 +24,7 @@ I love Ansible and I'm pretty happy to have this configuration management soluti
 
 I've finished the first steps really quickly. After I've added a script for my home lab Proxmox VE host and a static inventory for a bunch of my Raspberries, I did a check with `ansible-inventory -i inventory/ --list` and everything seems to be working as expected. All my hosts were listed and Ansible groups were applied as well. But here comes the clue: The test Playbook run failed, it looks like Ansible was not able to find the required variables. What the heck...
 
-{{< hint info >}}
+{{< hint type=note >}}
 **Pro tip**\
 There is one thing you should keep in mind, variables are related to the inventory file(s) or Playbooks.
 {{< /hint >}}