<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Source of Truth on dominic.dev</title>
    <link>https://www.dominic.dev/tags/source-of-truth/</link>
    <description>Recent content in Source of Truth on dominic.dev</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 23 Feb 2026 16:58:04 +0200</lastBuildDate>
    <atom:link href="https://www.dominic.dev/tags/source-of-truth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WIP: Ansible and Netbox</title>
      <link>https://www.dominic.dev/talks/2021-09-28-wip-ansible-netbox/</link>
      <pubDate>Tue, 28 Sep 2021 18:00:00 +0200</pubDate>
      <guid>https://www.dominic.dev/talks/2021-09-28-wip-ansible-netbox/</guid>
      <description>&lt;p&gt;Tracking IPs, networks, servers, and virtual machines manually in Excel and Confluence creates an airgap that prevents seamless automation. I shared our journey to bridge this gap during my talk at the 10th Ansible Meetup in Zurich. As we pushed for wider adoption of configuration management, we realized we needed a robust source of truth inventory, leading us to migrate to Netbox for IPAM and device management. Here is a breakdown of how Netbox and Ansible integrate, how context data is structured, and why we sometimes have to bypass modules to interact directly with the API.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
