<?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>Ansible on Dennis Mwangi</title><link>https://dennismwangi.com/tags/ansible/</link><description>Recent content in Ansible on Dennis Mwangi</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dennismwangi.com/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>NetDevOps Pipeline Part 2: Building a Dynamic Inventory with Ansible and NetBox</title><link>https://dennismwangi.com/posts/ansible-netbox-integration/</link><pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate><guid>https://dennismwangi.com/posts/ansible-netbox-integration/</guid><description>&lt;p&gt;By default, Ansible relies on static inventory files (&lt;code&gt;hosts.ini&lt;/code&gt; or &lt;code&gt;hosts.yaml&lt;/code&gt;). In a dynamic, modern network environment, managing these text files manually becomes an operational nightmare.&lt;/p&gt;
&lt;p&gt;To bridge this gap, we can tie Ansible&amp;rsquo;s execution directly to NetBox, using it as our single source of truth. Before we configure the plugin, your local control machine needs the official NetBox collection along with its underlying Python API wrapper and timezone dependencies:&lt;/p&gt;</description></item></channel></rss>