Typo in image link

posts/2023-09-21-graduating-automation/index.html

@@ -198,7 +198,7 @@ <h1>Graduating with Automation Practices</h1>
 <p>There&rsquo;s a variety of methods available to do this, I&rsquo;ve written an <a href="https://github.com/aludwar/ansible/blob/master/metrics/export_host_variables.yml">example playbook</a> that illustrates how this can be done. Using a report like this can help you group together common configuration artifacts like NTP server, DNS information, device services or purpose, etc. Using this information combined with the above helps you decide what commonality may exist across hosts. This can help you better define what should be handled in a host_var, group_var, role or default var, etc. Putting this in a text format helps you build a directory folder scaffolding structure for these common configuration artifacts and logic. A resource that can help in this area is the Ansible Variable Precedence order. Using this as a reference, you can decide where host variable classification should be, what might make sense as a sane default with other variable options that have an option to supersede it. For example:</p>
 </li>
 </ol>
-<p><img src="https://calgaryrhce.ca/wp-content/uploads/2023/09/ansiblevariableprededence.png" alt="Ansible Variables Precedence"></p>
+<p><img src="https://calgaryrhce.ca/wp-content/uploads/2024/09/ansiblevariableprecedence.png" alt="Ansible Variables Precedence"></p>
 <ul>
 <li>You may have NTP or DNS servers specific to a geographical region. These may make the most sense to include in the inventory group_vars. However, there may be some subregions like a DMZ that may have a different entry for this that is better placed in an inventory host_vars level.</li>
 <li>You may have common configurations specific to RHEL7, RHEL8, RHEL9, or Windows Server 2016, 2019, 2022, etc. that might be appropriate for a role default value.</li>