<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>XLAB Steampunk Home</title><link>https://steampunk.si/</link><description>Recent content on XLAB Steampunk Home</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Nov 2026 14:05:42 +0000</lastBuildDate><atom:link href="https://steampunk.si/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing Ansible Playbooks and Infrastructure</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Streamlining Ansible Playbook Migration and Upgrade for One of the Top Global FSIs with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Achieve 350% One-Year ROI with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How Spotter enabled Computer Space to scale its Ansible automation projects and create a centralized quality framework</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Efficient Ansible and Terraform Script Management</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>MindPoint Group and XLAB Steampunk Join Forces for Enhanced Security Compliance Automation</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Scale Computing accelerates customer adoption with Ansible integration</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Steampunk Spotter vs. Ansible Lint: Comparison</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Automate for Efficiency &amp; Growth</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How Deutsche Telekom MMS optimizes Ansible Playbooks with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Automate your security with Ansible</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>One of Slovenia's largest Financial Services Companies automated infrastructure with Ansible</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Unified Security and Compliance Across Ansible and Terraform</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Continuous Security and Compliance for Enterprise Automation</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How Computer Space leverages Steampunk Spotter to supercharge productivity</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Increase your product value with Ansible integrations</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Ansible integration helps Sensu reach more users</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Ensure reliable and secure automation</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>The importance of high-quality Ansible Collections for your product</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Steampunk Spotter Demo</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to run a scan with Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to set scan profiles with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to set custom rules with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>SBOM &amp; CVE Analysis for Ansible Collections</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to Manage Supply Chain Management with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Maximize bussiness value with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Streamline Ansible Automation with Red Hat AAP</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Validate Ansible Playbooks in Managed Red Hat AAP</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to skip or enforce checks with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Report &amp; Secure Your Ansible Automation with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Easily identify and fix playbook issues in Red Hat AAP</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Steampunk Spotter Visual Studio Code extension: Setup and scanning</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to use Steampunk Spotter to simplify Ansible upgrades</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to automatically fix Ansible content with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Assisted Playbook Writing feature</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Spotter App quick overview</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Security Checks</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to assure compliance of your Ansible Playbooks</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Insights for your scans</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Easily upgrade to the latest Ansible version</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>How to scan public Git repositories with Steampunk Spotter</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Working with projects</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Simplify and Speed up Ansible Upgrades</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Quickly apply fixes to your playbooks</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description/></item><item><title>Shift-left security for Terraform: checking configurations and plans in CI/CD</title><link>https://steampunk.si/spotter/blog/shift-left-security-terraform-cicd/</link><pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/shift-left-security-terraform-cicd/</guid><description>&lt;p&gt;With the latest release, Steampunk Spotter checks Terraform plans before apply, in addition to Terraform configurations at merge request. It enforces built-in checks and your custom policies on the resolved plan, flags secrets left in cleartext, and validates code against the definitions of official Terraform providers.&lt;/p&gt;
&lt;p&gt;This closes the gap that code review leaves open. A reviewer sees what someone wrote, but the real change and any sensitive values in it only become visible once Terraform resolves the plan. Now Spotter checks both, inside the CI/CD pipeline you already run.&lt;/p&gt;</description></item><item><title>Never Deploy Broken Playbooks Again: Ansible Automation Platform and Steampunk Spotter Integration</title><link>https://steampunk.si/spotter/blog/never-deploy-broken-playbooks-again-aap-spotter-integration/</link><pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/never-deploy-broken-playbooks-again-aap-spotter-integration/</guid><description>&lt;p&gt;Imagine confidently deploying Ansible Playbooks knowing they&amp;rsquo;re free of security vulnerabilities and compliance issues. With &lt;strong&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
&lt;/strong&gt; integrated into Red Hat Ansible Automation Platform (AAP), &lt;strong&gt;every job is checked against your company’s policies before and even during execution,&lt;/strong&gt; and only compliant automation gets to run.&lt;/p&gt;
&lt;p&gt;Let’s look at how the integration works and what it brings to your workflow.&lt;/p&gt;
&lt;h2 id="why-integrate-ansible-automation-platform-with-steampunk-spotter"&gt;Why Integrate Ansible Automation Platform with Steampunk Spotter?&lt;/h2&gt;
&lt;p&gt;Before diving into the specifics, let&amp;rsquo;s explore why these powerful platforms work best together. While code checking tools help us validate Ansible Playbooks before execution which significantly shortens debugging time and prevents major production issues, the truth is that &lt;strong&gt;static code analysis and early fail principle still fall short.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Red Hat Connect London 2026: See Spotter MCP Check AI-Written Code Live</title><link>https://steampunk.si/spotter/blog/red-hat-connect-london-2026/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/red-hat-connect-london-2026/</guid><description>&lt;p&gt;XLAB Steampunk is coming to &lt;strong&gt;Red Hat Connect London on October 8, 2026!&lt;/strong&gt; Meet us at &lt;strong&gt;booth #6&lt;/strong&gt; to see how to govern your Ansible and Terraform code, whether an engineer or an AI agent wrote it. We’ll reveal Spotter MCP, which lets an AI coding agent check its own code with Steampunk Spotter as it writes it, and we&amp;rsquo;ll run it live.&lt;/p&gt;
&lt;p&gt;If your team is using more AI in automation work and wants to keep standards consistent, come and talk to us. We&amp;rsquo;ll walk you through it with your own stack in mind.&lt;/p&gt;</description></item><item><title>AI-Generated Ansible Playbooks: What Our Q3 2026 Report Found</title><link>https://steampunk.si/spotter/blog/ai-generated-ansible-playbooks-what-our-q3-2026-report-found/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ai-generated-ansible-playbooks-what-our-q3-2026-report-found/</guid><description>&lt;p&gt;For our Q3 2026 AI Model Leaderboard, we asked &lt;strong&gt;DeepSeek-V4-Flash, claude-sonnet-5, and gpt-5.6-terra&lt;/strong&gt; to generate playbooks for the same three tasks, a simple Nginx site, a ten-switch Cisco Catalyst rollout, and a full Ansible 2.4-to-2.14 upgrade, and then ran everything they produced through Steampunk Spotter, our governance and guardrail platform for AI-generated Ansible and Terraform code.&lt;/p&gt;
&lt;p&gt;The result: &lt;strong&gt;140 errors, 94 warnings, and 221 hints across nine runs.&lt;/strong&gt;&lt;/p&gt;
&lt;/br&gt; 
&lt;h2 id="capability-didnt-prevent-mistakes"&gt;Capability didn&amp;rsquo;t prevent mistakes&lt;/h2&gt;
&lt;p&gt;The most consistent problem across all three scenarios came from claude-sonnet-5. It kept writing short module names instead of fully qualified collection names (FQCN) — 12 times in the easiest scenario, 17 times in the mid-complexity scenario, and 27 times in the hardest one.&lt;/p&gt;</description></item><item><title>The Risk Isn't AI. It's Ungoverned Automation.</title><link>https://steampunk.si/spotter/blog/the-risk-is-not-ai-it-is-ungoverned-automation/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/the-risk-is-not-ai-it-is-ungoverned-automation/</guid><description>&lt;p&gt;A single misconfigured Ansible Playbook can touch thousands of systems in seconds. A single untested Terraform change can do the same to a cloud environment. That&amp;rsquo;s always been true. What&amp;rsquo;s changed is who&amp;rsquo;s writing the code that reaches that point — and how fast it&amp;rsquo;s arriving.&lt;/p&gt;
&lt;p&gt;GitHub Copilot, ChatGPT, Claude Code, and a growing wave of autonomous agents are now generating real chunks of the automation running in production. You’re not going to slow that down. You can only decide how to handle what it produces. AI assistants write faster than any team could, and most of what they produce is genuinely useful. But speed at the authoring stage doesn&amp;rsquo;t mean anything about what happens at the execution stage. Somewhere between &amp;ldquo;AI wrote this&amp;rdquo; and &amp;ldquo;this just ran in production,&amp;rdquo; someone still has to decide whether it&amp;rsquo;s allowed to run at all.&lt;/p&gt;</description></item><item><title>Steampunk Spotter: Bringing governance into your CI/CD pipeline</title><link>https://steampunk.si/spotter/blog/bringing-governance-into-your-cicd-pipeline/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/bringing-governance-into-your-cicd-pipeline/</guid><description>&lt;p&gt;Your infrastructure code already has a pipeline. Probably two — one that ships Ansible Playbooks, one that runs &lt;code&gt;terraform apply&lt;/code&gt; — and somewhere in each, someone is supposed to be checking whether the change is safe. Usually that someone is a senior engineer with too many tabs open.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the governance gap. Not a missing tool, but a missing decision point. Standards exist — in a wiki page, a Confluence doc, or the head of whoever wrote the first playbook. Review happens, but it depends on who&amp;rsquo;s on shift and how big the diff is. Nothing in the pipeline actually stops content from reaching production because it broke a rule.&lt;/p&gt;</description></item><item><title>Meet McChain: The Spotter Crew's Supply Chain Manager</title><link>https://steampunk.si/spotter/blog/meet-the-spotter-crews-supply-chain-manager-mcchain/</link><pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/meet-the-spotter-crews-supply-chain-manager-mcchain/</guid><description>&lt;p&gt;Every crew needs someone who builds the foundation before anything else can run. On the Spotter Crew, that’s McChain — and nothing gets bolted into the chain until he’s checked it first.&lt;/p&gt;
&lt;h2 id="who-is-mcchain"&gt;Who is McChain?&lt;/h2&gt;
&lt;p&gt;McChain is the Spotter Crew’s &lt;strong&gt;Supply Chain Manager.&lt;/strong&gt; You&amp;rsquo;d know him anywhere by the handlebar moustache — his trademark. The rest of him is built for the work: a boiler-bodied machine with side platforms and brass cogs, a gooseneck crane arm, and a chain with a claw grip for hauling components into place, backed by a panel of gauges and dials that checks every link before it&amp;rsquo;s allowed through. He works out of a highly organized logistics center, where every check that passes through the crew gets stored and categorized before it moves on.&lt;/p&gt;</description></item><item><title>AAP 2.7 Upgrade Readiness – What to Check Before You Upgrade</title><link>https://steampunk.si/spotter/blog/aap-2-7-upgrade-readiness/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/aap-2-7-upgrade-readiness/</guid><description>&lt;p&gt;Every AAP upgrade looks manageable on paper — version bump, new features, a timeline mapped before the project kicked off. What never makes it into the plan is the Playbook estate. The platform upgrades. Your Playbooks don’t. Everything written against older Ansible Core versions, older module APIs, or assumptions that were valid two years ago stays exactly where it is, until the first job runs on the new platform and something breaks.&lt;/p&gt;</description></item><item><title>Meet Rulus: The Spotter Crew's Compliance Inspector</title><link>https://steampunk.si/spotter/blog/meet-the-spotter-crews-compliance-inspector-rulus/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/meet-the-spotter-crews-compliance-inspector-rulus/</guid><description>&lt;p&gt;Every crew needs someone who never bends the rules. On the Spotter Crew, that someone is Rulus — and he wouldn&amp;rsquo;t have it any other way.&lt;/p&gt;
&lt;h2 id="who-is-rulus"&gt;Who is Rulus?&lt;/h2&gt;
&lt;p&gt;Rulus is the Spotter Crew&amp;rsquo;s Compliance Inspector. Tall, cloaked, and unmistakably commanding, he moves through the central monitoring chamber with the unhurried certainty of someone who knows exactly what the rules are — and exactly who&amp;rsquo;s breaking them.&lt;/p&gt;
&lt;p&gt;His most distinctive feature is his head: three large cylindrical lenses arranged in a triangular formation, each glowing with a warm, watchful light. They don&amp;rsquo;t miss a thing. While the rest of the crew might pause for banter or the occasional coffee break, Rulus is already three playbooks ahead, scanning for anything out of line.&lt;/p&gt;</description></item><item><title>AI-Generated Ansible Playbooks: Where AI Helps and Where It Breaks</title><link>https://steampunk.si/spotter/blog/ai-generated-ansible-playbooks-where-ai-helps-and-where-it-breaks/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ai-generated-ansible-playbooks-where-ai-helps-and-where-it-breaks/</guid><description>&lt;p&gt;The AI-generated Ansible Playbook arrives in seconds. The problem is that &amp;rsquo;looks right&amp;rsquo; and &amp;lsquo;works in production&amp;rsquo; aren&amp;rsquo;t the same thing — and at scale, the gap between them is where outages live.&lt;/p&gt;
&lt;p&gt;Generative AI is already changing how DevOps and platform teams write automation. Tools like Ansible Lightspeed, Copilot, and general-purpose LLMs are accelerating the most tedious parts of Ansible work — drafting tasks, translating shell into modules, scaffolding roles. That’s real productivity. But the same speed that helps a senior engineer can quietly mislead a less experienced one. AI doesn’t know which modules your organization has approved. It doesn’t know which collections you’ve vendored. It doesn’t always know which syntax is current and which got deprecated two minor versions ago.&lt;/p&gt;</description></item><item><title>Red Hat Summit 2026: Automation Governance Takes Center Stage</title><link>https://steampunk.si/spotter/blog/red-hat-summit-2026-recap/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/red-hat-summit-2026-recap/</guid><description>&lt;p&gt;Red Hat Summit is always a useful signal for where the industry is actually heading — not just where vendors say it&amp;rsquo;s going. This year in Atlanta, the signal was unusually clear. If there was one theme that ran through every keynote, every hallway conversation, and every breakout session at Summit 2026, it was this: the age of &amp;ldquo;move fast and fix it later&amp;rdquo; in automation is over.&lt;/p&gt;
&lt;p&gt;We were there. Here is what stood out.&lt;/p&gt;</description></item><item><title>How SWIFT Governs Ansible Automation and Modernizes 2,000 Playbooks</title><link>https://steampunk.si/spotter/blog/inside-swifts-plan-to-modernize-thousands-of-ansible-playbooks/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/inside-swifts-plan-to-modernize-thousands-of-ansible-playbooks/</guid><description>&lt;p&gt;SWIFT runs Ansible automation that touches roughly one third of global GDP every day, so Ansible automation governance is a baseline engineering requirement for them. At Red Hat Summit 2026, SWIFT shared how they’re rolling it out. The plan has three parts: a 2.9 to 2.16 migration of ~2,000 Ansible Playbooks, risk assessment of third-party collections, and policy checks on every Playbook before it reaches production.&lt;/p&gt;
&lt;p&gt;Their environment spans tens of thousands of VMs, network devices in production and elevated privileges across production systems. Every Playbook they run is effectively a software supply chain. SWIFT is the secure financial messaging backbone for 11,000+ financial institutions in more than 200 countries.&lt;/p&gt;</description></item><item><title>Meet the Spotter Crew’s AI Generative Mind - Genna</title><link>https://steampunk.si/spotter/blog/meet-the-spotter-crews-ai-generative-mind-genna/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/meet-the-spotter-crews-ai-generative-mind-genna/</guid><description>&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-scav/"&gt;Scav&lt;/a&gt;
 scans your playbooks. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-reeva/"&gt;Reeva&lt;/a&gt;
 rewrites what’s broken. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-chuck/"&gt;Chuck&lt;/a&gt;
 decides which checks run. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-dash/"&gt;Dash&lt;/a&gt;
 makes sure you understand it all.&lt;/p&gt;
&lt;p&gt;But scanning and rewriting only go as far as the rules allow. And when your organization has requirements that aren&amp;rsquo;t covered yet — compliance needs that no default policy addresses — someone has to write them.&lt;/p&gt;
&lt;p&gt;That’s Genna’s world.&lt;/p&gt;
&lt;h2 id="meet-genna-the-architect-of-policies-that-never-existed-before"&gt;Meet Genna: The Architect of Policies That Never Existed Before&lt;/h2&gt;
&lt;p&gt;The Spotter Crew was already exceptional at enforcement. But all of that power rested on one assumption: the policies already existed. That someone had written the rules.&lt;/p&gt;</description></item><item><title>What’s new in Spotter: Terraform Support and Extended Compliance Validation</title><link>https://steampunk.si/spotter/blog/terraform-support-and-extended-compliance-validation/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/terraform-support-and-extended-compliance-validation/</guid><description>&lt;p&gt;We&amp;rsquo;re excited to share the latest updates to Steampunk Spotter. This round of releases brings the biggest expansion Spotter has seen since its launch: Terraform support, a redesigned compliance validation experience built around CIS Benchmarks and AI-generated policies, and a brand-new usage report that gives you visibility into how your teams are actually using Spotter. And this release adds support for the latest Ansible Core 2.20, so your teams stay current with the newest Ansible without missing a beat.&lt;/p&gt;</description></item><item><title>The Real Challenges of Ansible Upgrades — And How Top Teams Solve Them</title><link>https://steampunk.si/spotter/blog/how-top-teams-solve-the-real-challenges-of-ansible-upgrades/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-top-teams-solve-the-real-challenges-of-ansible-upgrades/</guid><description>&lt;p&gt;Upgrading your Ansible environment is not something you can postpone indefinitely. Eventually, outdated playbooks slow you down. Imagine trying to manually review 2,300 playbooks before a migration deadline. That&amp;rsquo;s the reality for most enterprise Ansible teams — and most of them have no tooling in place to make it manageable.&lt;/p&gt;
&lt;/br&gt;
&lt;h2 id="why-ansible-upgrades-are-harder-than-they-look"&gt;Why Ansible upgrades are harder than they look&lt;/h2&gt;
&lt;p&gt;Enterprise Ansible environments are rarely tidy. When migrating from Tower or AWX to the Ansible Automation Platform (AAP), teams run into a set of compounding challenges:&lt;/p&gt;</description></item><item><title>The Complete Guide to Ansible Upgrade and Migration</title><link>https://steampunk.si/spotter/blog/complete-guide-to-ansible-upgrade-migration/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/complete-guide-to-ansible-upgrade-migration/</guid><description>&lt;p&gt;Upgrading your Ansible environment is not something you can postpone indefinitely.&lt;/p&gt;
&lt;p&gt;Eventually, outdated playbooks slow you down. Things break. Security risks emerge. What once worked perfectly becomes difficult to maintain or even understand.&lt;/p&gt;
&lt;p&gt;If you are planning to move to Red Hat Ansible Automation Platform 2+ or simply upgrading your playbooks to a newer Ansible version, you are likely facing both technical uncertainty and operational pressure.&lt;/p&gt;
&lt;p&gt;This guide consolidates everything you need in one place. It will help you understand how to approach upgrades, identify where the real complexity lies, and make the process faster, safer, and more predictable.&lt;/p&gt;</description></item><item><title>The Ultimate Guide to Securing Ansible Supply Chain</title><link>https://steampunk.si/spotter/blog/ultimate-guide-to-securing-ansible-supply-chain/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ultimate-guide-to-securing-ansible-supply-chain/</guid><description>&lt;p&gt;Most Ansible Playbooks rely on more than the code in the playbook itself, such as collections, roles, Python packages and container images. If one of those pieces is vulnerable or tampered with, your automation spreads the problem to every system it touches. This guide covers where Ansible supply chain risks hide, the controls that stop them, and the best practices that keep your automation safe.&lt;/p&gt;
&lt;h3 id="tldr-ansible-supply-chain-in-5-steps"&gt;TL;DR: Ansible supply chain in 5 steps&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Pin the exact versions of every collection and package you use.&lt;/li&gt;
&lt;li&gt;Install content only from trusted, signed sources, and verify the signatures.&lt;/li&gt;
&lt;li&gt;Build execution environments from pinned images and scan them for known vulnerabilities (CVEs).&lt;/li&gt;
&lt;li&gt;Keep a Software Bill of Materials (SBOM) so you know what’s inside your automation.&lt;/li&gt;
&lt;li&gt;Check every change against your security policy in CI/CD before it reaches production.&lt;/li&gt;
&lt;/ol&gt;
&lt;/br&gt;
&lt;h2 id="what-does-shift-left-mean-in-ansible-security"&gt;What does “shift left” mean in Ansible security?&lt;/h2&gt;
&lt;p&gt;“Shift left” is a term that comes from software development. Traditionally, security checks happen late—during production or after deployment. Shifting left means &lt;strong&gt;embedding security earlier in the lifecycle,&lt;/strong&gt; during design, development, and testing.&lt;/p&gt;</description></item><item><title>Securing Ansible Playbooks and Infrastructure</title><link>https://steampunk.si/spotter/ebooks/securing-ansible-playbooks-and-infrastructure/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/ebooks/securing-ansible-playbooks-and-infrastructure/</guid><description>&lt;h3 id="inside-the-e-book"&gt;Inside the e-book:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Why security must start early&lt;/b&gt; in Ansible automation&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Managing security risk&lt;/b&gt; across the Ansible dependency chain&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Common security risks&lt;/b&gt; in Ansible Playbooks&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Security risks beyond playbooks:&lt;/b&gt; the Ansible infrastructure layer&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Best practices&lt;/b&gt; for securing the Ansible supply chain&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;A secure &lt;b&gt;Ansible workflow in practice&lt;/b&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Building governance&lt;/b&gt; into the Ansible workflow&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;b&gt;Tools and technology&lt;/b&gt; for shifting security left in Ansible&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>5 Best Ansible Playbook Scanning Tools in 2026 for Secure and Scalable Automation</title><link>https://steampunk.si/spotter/blog/five-best-ansible-playbook-scanning-tools/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/five-best-ansible-playbook-scanning-tools/</guid><description>&lt;p&gt;As Ansible adoption increases across organizations, automation is no longer limited to a few playbooks managed by a single team. Many enterprises operate Ansible at scale, with hundreds of playbooks, multiple teams contributing automation, and critical infrastructure changes occurring daily.&lt;/p&gt;
&lt;p&gt;This shift brings new challenges. Release cycles are faster, Ansible Core and Automation Platform upgrades happen more frequently, and security and compliance requirements are increasingly enforced directly in CI/CD pipelines. At the same time, automation must be auditable, predictable, and safe, especially when it affects production systems.&lt;/p&gt;</description></item><item><title>Meet Chuck - The Check Manager of Spotter Crew</title><link>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-chuck/</link><pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-chuck/</guid><description>&lt;p&gt;It is 3 a.m., the office is silent, with only the hum of servers ..until the alerts start pouring in. Red, yellow, green. Chaos fills every corner of the pipeline. The automation team groans. They have seen this before.&lt;/p&gt;
&lt;p&gt;Then Chuck appears – not through a door, not on a screen, but like a force of nature. Gravelly voice, leather jacket, axe in hand. He is here to bring the mess under control. He does not run the checks himself; he commands them. He decides which checks step out of the closet, which enter the playbooks, and which light up anything that is not okay.&lt;/p&gt;</description></item><item><title>Secure Your Ansible Automation: Introducing SBOM, CVE Analysis, and Security Reports</title><link>https://steampunk.si/spotter/blog/introducing-SBOM-CVE-analysis/</link><pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/introducing-SBOM-CVE-analysis/</guid><description>&lt;h2 id="what-is-sbom"&gt;What is SBOM?&lt;/h2&gt;
&lt;p&gt;A Software Bill of Materials (SBOM) is essentially the list of elements in your software. Just as a food label indicates ingredients, an SBOM provides a detailed inventory of the components, libraries and dependencies in your applications, automation environments, or playbooks.&lt;/p&gt;
&lt;p&gt;At its core, an SBOM is a structured record of all parts that make up a piece of software. This includes open-source libraries, proprietary code and licensed third-party dependencies. A comprehensive SBOM can also capture details about the build process, such as the tools and environments used.&lt;/p&gt;</description></item><item><title>Automate your Ansible upgrade and migration process</title><link>https://steampunk.si/spotter/blog/automate-upgrade-and-migration-process/</link><pubDate>Thu, 28 Aug 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/automate-upgrade-and-migration-process/</guid><description>&lt;p&gt;Upgrading your Ansible playbooks is not a “someday-maybe” project, it’s essential. Sticking with outdated playbooks reduces ROI, slows automation adoption, and introduces security risks.&lt;br&gt;
Manual upgrades may seem simple, but every step carries the risk of errors, inconsistencies, and downtime.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Automation eliminates these risks, and quickly ensures accurate, compliant, and reliable results.&lt;/strong&gt; This guide breaks down the upgrade and migration process into 5 key steps that will help you create AAP-compliant playbooks ready for Red Hat Ansible Automation Platform 2.4+ and Ansible 2.15+.&lt;/p&gt;</description></item><item><title>Integrating Steampunk Spotter with Azure DevOps Pipelines</title><link>https://steampunk.si/spotter/blog/integrating-steampunk-spotter-with-azure-devops-pipelines/</link><pubDate>Tue, 29 Jul 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/integrating-steampunk-spotter-with-azure-devops-pipelines/</guid><description>&lt;p&gt;Want to catch deprecated code, security issues, or compliance problems before they hit your main branch? With native support for Azure Pipelines, &lt;strong&gt;Steampunk Spotter&lt;/strong&gt; brings automation and actionable feedback directly into your CI/CD workflows—now with seamless integration into Azure DevOps.&lt;/p&gt;
&lt;p&gt;In this blog post, we’ll walk you through how to utilize Steampunk Spotter from your Azure DevOps project and scan your Ansible content automatically with every pipeline run.&lt;/p&gt;
&lt;br/&gt;
&lt;h3 id="step-1-set-up-your-azure-devops-project"&gt;Step 1: Set Up Your Azure DevOps Project&lt;/h3&gt;
&lt;p&gt;Start by creating a new project in Azure DevOps. Once created, navigate to the &lt;strong&gt;Repos&lt;/strong&gt; section in the sidebar to push your initial code.&lt;/p&gt;</description></item><item><title>What’s top of mind for Ansible users: Insights from the summit floor</title><link>https://steampunk.si/spotter/blog/insights-from-the-summit-floor/</link><pubDate>Thu, 17 Jul 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/insights-from-the-summit-floor/</guid><description>&lt;p&gt;This year’s Red Hat Summit once again brought together thousands of automation experts, enterprise IT leaders and open source enthusiasts to exchange ideas, showcase solutions and explore the future of IT automation. We hosted interactive polls at our booth, shared insights during our breakout session, and gathered some insightful learnings about where automation is headed.&lt;/p&gt;
&lt;p&gt;Here are two insights that stood out.&lt;/p&gt;
&lt;h2 id="63-have-already-adopted-aap-due-to-the-need-for-scalable-automation"&gt;63% have already adopted AAP due to the need for scalable automation&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Which Ansible do you use?&lt;/strong&gt; We asked this question to attendees at our booth—and here’s what we learnt:&lt;/p&gt;</description></item><item><title>Meet the Spotter Crew’s Data Storyteller – Dash 804RD</title><link>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-dash/</link><pubDate>Tue, 24 Jun 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-dash/</guid><description>&lt;p&gt;Scav finds the problems. Reeva fixes them. But who makes sure you understand what was found, what was fixed and what it all means?&lt;/p&gt;
&lt;p&gt;Dash 804RD is the Spotter Crew’s storyteller and makes the data talk. With every chart, every pulse and every insight, Dash transforms the chaos of automation into something readable, actionable and real. He’s the one who helps you understand what the Spotter Crew has uncovered — and why it matters.&lt;/p&gt;</description></item><item><title>Implementing quality automation at scale with Steampunk Spotter: Step-by-step guide</title><link>https://steampunk.si/spotter/blog/implementing-quality-automation-at-scale-with-steampunk-spotter-step-by-step-guide/</link><pubDate>Thu, 12 Jun 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/implementing-quality-automation-at-scale-with-steampunk-spotter-step-by-step-guide/</guid><description>&lt;p&gt;Computer Space, a leading IT solutions provider, faced increased complexity in managing large-scale Ansible automation for clients in the banking sector. With hundreds of Ansible Playbooks distributed across teams and repositories, ensuring consistent code quality became a serious challenge.&lt;/p&gt;
&lt;p&gt;By implementing Steampunk Spotter as part of their automation framework, Computer Space &lt;strong&gt;was able to transform bank’s development workflow, increase productivity from a few automation projects to more than 20 automation projects, and establish a centralized quality control system that benefits both their team and the bank&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Meet the Spotter Crew’s Rewrite Genius – Reeva</title><link>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-reeva/</link><pubDate>Tue, 10 Jun 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-reeva/</guid><description>&lt;p&gt;We’ve already introduced Scav, the Chief Scanning Officer of the Spotter Crew — the one who finds every flaw in the playbooks. But finding problems is only half the story.&lt;/p&gt;
&lt;p&gt;Today, we’re turning the spotlight on the one who makes sure those problems never stay broken: Reeva, the Rewrite Genius of flawless code.&lt;/p&gt;
&lt;p&gt;When outdated, broken, or chaotic playbooks threaten your automation, Reeva steps in with speed, precision, and a spark of brilliance. She’s the master of rewrites and repairs, and no one — absolutely no one — fixes things like she does.&lt;/p&gt;</description></item><item><title>Steampunk take on Red Hat Summit 2025</title><link>https://steampunk.si/spotter/blog/steampunk-take-on-rhs-2025/</link><pubDate>Wed, 28 May 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-take-on-rhs-2025/</guid><description>&lt;p&gt;From May 19–22 , Boston hosted this year’s Red Hat Summit and Ansible Fest—an open-source technology gathering that brought together Red Hat and Ansible enthusiasts from around the world. With a dynamic mix of live sessions, hands-on labs, product roadmaps, and partner ecosystem presentations, Red Hat Summit attendees had the chance to learn what’s next for the future of open source.&lt;/p&gt;
&lt;p&gt;We were thrilled to be there as a proud sponsor and active member of the Ansible community, sharing insights, exchanging ideas, and enjoying conversations with industry peers.&lt;/p&gt;</description></item><item><title>The Spotter Crew Release: Meet Scav</title><link>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-scav/</link><pubDate>Tue, 13 May 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/the-spotter-crew-release-meet-scav/</guid><description>&lt;p&gt;Have you ever wondered how Steampunk Spotter, the Ansible Playbook Platform, actually works? How is playbook scanning executed, how are automated codes achieved, and how is the right check enforced, all in line with your company standards?&lt;/p&gt;
&lt;p&gt;Well, it’s not just powerful technology. Behind this powerful automation machine there is a whole crew of specialized characters, each tasked with solving specific challenges in your Ansible workflow.&lt;/p&gt;
&lt;p&gt;From code scanning and validation to rewriting and dependency control, the &lt;strong&gt;Spotter Crew&lt;/strong&gt; works behind the scenes to keep your Ansible content up-to-date and reliable.&lt;/p&gt;</description></item><item><title>Achieve Compliant and Secure Ansible Automation – Explore Steampunk Spotter New Features</title><link>https://steampunk.si/spotter/blog/explore-steampunk-spotter-new-features/</link><pubDate>Wed, 07 May 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/explore-steampunk-spotter-new-features/</guid><description>&lt;p&gt;We’re excited to introduce the latest updates to Steampunk Spotter. These new features give you even more control over your Ansible Playbooks — saving you time on manual reviews and ensuring consistent and validated Ansible content for all your workflows.&lt;/p&gt;
&lt;p&gt;From AI-Powered Compliance Validation to CVE Analysis and Security Reports for Ansible Collections, these new features make it easier than ever to automate your playbooks and optimize compliance and security across your organization.&lt;/p&gt;</description></item><item><title>Supply Chain Management 101: Securing Your Ansible Automation with Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/supply-chain-management-101-securing-your-ansible-automation-with-steampunk-spotter/</link><pubDate>Wed, 05 Mar 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/supply-chain-management-101-securing-your-ansible-automation-with-steampunk-spotter/</guid><description>&lt;p&gt;In the fast-paced world of IT automation, managing third-party dependencies in your Ansible workflows is a crucial security and compliance challenge. The modern software supply chain is more complex than ever, with a growing risk of vulnerabilities, compromised dependencies, and outdated components sneaking into your infrastructure.&lt;/p&gt;
&lt;p&gt;That’s where &lt;strong&gt;Steampunk Spotter’s Supply Chain Management&lt;/strong&gt; feature comes in—a powerful enterprise-level tool that gives you complete control over which dependencies can be installed or used in your Ansible Playbooks. Whether it’s a specific Python version, an Ansible collection, or an individual module, Spotter helps you enforce security policies to mitigate risks before they become critical issues.&lt;/p&gt;</description></item><item><title>Spotter Custom Policies 104: Accelerating Policy Development for Spotter with ChatGPT</title><link>https://steampunk.si/spotter/blog/accelerating-policy-development-for-spotter-with-chatgpt/</link><pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/accelerating-policy-development-for-spotter-with-chatgpt/</guid><description>&lt;p&gt;In the evolving world of DevOps, ensuring Ansible playbooks adhere to security best practices and internal compliance rules is crucial. Steampunk Spotter provides a robust platform for validating these playbooks, including the ability to enforce &lt;strong&gt;custom policies written in Rego&lt;/strong&gt;, which h already utilised and created a workflow to detect 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/preventing-PII-leaks-in-ansible-playbooks/"&gt;Personal Identifiable Information leakage detection&lt;/a&gt;
. But Sarah, has now discovered an even more efficient way to craft these policies — by leveraging GenAI (for example ChatGPT, Gemini or DeepSeek and ect.) to accelerate policy development.&lt;/p&gt;</description></item><item><title>Spotter Custom Policies 103: Preventing PII Leaks in Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/preventing-PII-leaks-in-ansible-playbooks/</link><pubDate>Thu, 06 Feb 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/preventing-PII-leaks-in-ansible-playbooks/</guid><description>&lt;p&gt;We&amp;rsquo;ve followed Sarah, a security compliance officer at a global enterprise, on her journey to securing Ansible Playbooks in previous posts. She tackled key security risks in 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/custom-policies-101-prevent-sensitive-data-leaks-in-playbooks/"&gt;Custom Policies 101: Preventing Sensitive Information Leakage in Your Playbooks&lt;/a&gt;
 and advanced her approach in 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/custom-policies-102-detecting-sensitive-data-in-variables-and-beyond/"&gt;Spotter Custom Policies 102: Detecting Sensitive Data in Variables and Beyond&lt;/a&gt;
.&lt;/p&gt;
&lt;p&gt;Now, Sarah is facing a new challenge: &lt;strong&gt;ensuring that sensitive parameters in playbooks, such as full names, passwords, and API keys, are always protected.&lt;/strong&gt; As she reviewed logs and configurations, Sarah discovered a worrying trend—sensitive personal data was being inadvertently leaked into logs, posing a major compliance and security risk. With regulatory pressures mounting, including GDPR and internal security policies, she needed a way to proactively detect and prevent these leaks before they reached production.&lt;/p&gt;</description></item><item><title>Spotter Custom Policies 102: Detecting Sensitive Data in Variables and Beyond</title><link>https://steampunk.si/spotter/blog/custom-policies-102-detecting-sensitive-data-in-variables-and-beyond/</link><pubDate>Wed, 22 Jan 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/custom-policies-102-detecting-sensitive-data-in-variables-and-beyond/</guid><description>&lt;p&gt;In our first post, 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/a-beginners-guide-to-tailored-automation-checks/"&gt;Spotter Custom Policies 101&lt;/a&gt;
, we explored how Steampunk Spotter&amp;rsquo;s custom policies empower teams to tailor their automation checks. Today, we’re diving deeper into a critical use case—detecting potential sensitive data across not just playbooks, but also variable files, and other related content.&lt;/p&gt;
&lt;p&gt;Modern IT environments are rich with automation, but they also pose unique security challenges. Ansible, as powerful as it is, doesn’t inherently prevent sensitive information from slipping into places it shouldn’t. Enter Spotter, with its ability to catch these vulnerabilities before they reach production.&lt;/p&gt;</description></item><item><title>Spotter Custom Policies 101: A Beginner’s Guide to Tailored Automation Checks</title><link>https://steampunk.si/spotter/blog/a-beginners-guide-to-tailored-automation-checks/</link><pubDate>Thu, 16 Jan 2025 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/a-beginners-guide-to-tailored-automation-checks/</guid><description>&lt;p&gt;Automation workflows often come with unique requirements that standard rules can’t always address. That’s where custom policies in 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;&lt;strong&gt;Steampunk Spotter&lt;/strong&gt;&lt;/a&gt;
 step in. Leveraging 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.openpolicyagent.org/"&gt;&lt;strong&gt;Open Policy Agent (OPA)&lt;/strong&gt;&lt;/a&gt;
 integration, Spotter empowers users to design tailored policies that enhance automation quality, security, and compliance.&lt;/p&gt;
&lt;p&gt;This blog post will introduce custom policies, why they matter, and walk you through creating your first custom policy in Spotter.&lt;/p&gt;
&lt;br/&gt;
&lt;h3 id="a-story-of-automation-excellence-meet-sarah"&gt;A Story of Automation Excellence: Meet Sarah&lt;/h3&gt;
&lt;p&gt;Sarah, a security compliance officer at a global enterprise, was tasked with auditing logs and preventing misconfigurations across the company’s infrastructure. One of Sarah’s focus areas was ensuring Ansible playbooks adhered to strict compliance and security standards. While the company used tools with pre-built checks, they weren’t sufficient to address the specific compliance needs of Sarah’s organization. When Sarh discovered the power of custom policies in 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;&lt;strong&gt;Steampunk Spotter&lt;/strong&gt;&lt;/a&gt;
, their workflow transformed.&lt;/p&gt;</description></item><item><title>XLAB Steampunk Partners with OceanBridge to Bring Cutting-Edge IT Automation to Japan</title><link>https://steampunk.si/spotter/blog/xlab-steampunk-partners-with-oceanbridge-to-bring-it-automation-to-japan/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/xlab-steampunk-partners-with-oceanbridge-to-bring-it-automation-to-japan/</guid><description>&lt;p&gt;We’re thrilled to announce our strategic partnership with OceanBridge Inc., a premier Japanese IT solutions provider. Through this collaboration, 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 - a platform designed to enhance the performance and security of Red Hat Ansible Automation - will now be available in the Japanese market. OceanBridge specializes in connecting international IT products with Japanese businesses, making it an ideal partner for XLAB Steampunk’s expansion.&lt;/p&gt;
&lt;figure&gt;
 
 &lt;img class="img-fluid"
 
 
 src="https://steampunk.si/spotter/blog/xlab-steampunk-partners-with-oceanbridge-to-bring-it-automation-to-japan/steampunk-oceanbridge-partnership.webp"
 width="1749" height="984"
 
 

 
 alt="Norikazu Sawa, President and CEO of OceanBridge Inc. and Gregor Berginc, CEO at XLAB &amp;amp; Head of XLAB Steampunk."
 
 /&gt;
 

 
 &lt;figcaption&gt;
 
 
 &lt;p&gt;
 Norikazu Sawa, President and CEO of OceanBridge Inc. and Gregor Berginc, CEO at XLAB &amp;amp; Head of XLAB Steampunk.
 
 &lt;/p&gt;</description></item><item><title>Steampunk Spotter 5.0: Supply Chain Management and Security Reports</title><link>https://steampunk.si/spotter/blog/supply-chain-management-and-security-reports/</link><pubDate>Wed, 30 Oct 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/supply-chain-management-and-security-reports/</guid><description>&lt;p&gt;Big things are happening with Steampunk Spotter this fall! We’re excited to introduce version 5.0, bringing major updates designed to give you &lt;strong&gt;more control, better security and easier management of Ansible automation projects.&lt;/strong&gt; The improved Spotter version focuses on boosting your productivity and making sure your automation stays secure and compliant with the latest standards.&lt;/p&gt;
&lt;p&gt;Let’s dive into the key highlights of Spotter 5.0.&lt;/p&gt;
&lt;h2 id="1-custom-scan-profiles"&gt;1. Custom Scan Profiles&lt;/h2&gt;
&lt;p&gt;Spotter 5.0 gives you the flexibility to create custom scan profiles tailored to your needs. Whether you’re working on different environments or projects, you can now pick which checks to include in a scan with just a few clicks. Additionally, we have added a detailed list of all checks included in each predefined scan profile, along with descriptions.&lt;/p&gt;</description></item><item><title>How to Ensure Only Secure and Approved Ansible Content is Used in Your Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/how-to-ensure-only-secure-and-approved-ansible-content/</link><pubDate>Thu, 24 Oct 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-to-ensure-only-secure-and-approved-ansible-content/</guid><description>&lt;p&gt;When building automation playbooks, Ansible Playbook security and compliance should be top priorities. However, managing dependencies - like specific versions of the Ansible runtime and Ansible Collections - can quickly become unmanageable.&lt;/p&gt;
&lt;p&gt;Steampunk Spotter’s Supply Chain Management feature enables teams to maintain strict control over the Ansible content used in their playbooks. This powerful solution empowers security teams to approve safe versions, block unapproved software, and enforce stringent policies. At the same time, playbook writers can focus on creating efficient, secure automation without needing deep Python expertise.&lt;/p&gt;</description></item><item><title>Upgrading your Ansible Playbooks: Step by step guide</title><link>https://steampunk.si/spotter/blog/upgrading-your-ansible-playbooks-step-by-step-guide/</link><pubDate>Mon, 21 Oct 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/upgrading-your-ansible-playbooks-step-by-step-guide/</guid><description>&lt;p&gt;Upgrading Ansible Playbooks and roles to the latest Ansible version can be quite a challenge, as a lot can change between versions (best practices alter, parameters and modules are moved or renamed, attributes are deprecated) … and the most challenging of all: you need to figure out what you were trying to accomplish with the playbook you wrote all those years ago. Or worse - you weren&amp;rsquo;t even the one who wrote it in the first place. And now you need to decide how to maintain the effect but upgrade the code.&lt;/p&gt;</description></item><item><title>Steampunk Spotter app: Gain Insights into Ansible Automation Performance, Health, and Security</title><link>https://steampunk.si/spotter/blog/keep-track-of-scan-history-and-collaborate-with-your-team/</link><pubDate>Tue, 23 Jul 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/keep-track-of-scan-history-and-collaborate-with-your-team/</guid><description>&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
, a powerful Ansible Playbook Platform, has an easy-to-use web interface called the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/login"&gt;Spotter App&lt;/a&gt;
 that allows you to gain insights into playbook performance, collaborate and manage teams in a shared workspace, tailor checks to your specific needs, and effectively optimize automation through a centralized platform. Let’s dive into Spotter App features.&lt;/p&gt;
&lt;figure class="ms-auto me-auto p-0"&gt;
&lt;a href="https://steampunk.si/spotter/#demo"&gt;
 &lt;img alt="Watch the Steampunk Spotter demo to analyze, improve, upgrade and secure Ansible Playbooks" width="820" height="90" class="p-0" src="Watch_Demo2.png" /&gt;
 &lt;/a&gt;
&lt;/figure&gt;
&lt;h2 id="analyze-scans"&gt;Analyze Scans&lt;/h2&gt;
&lt;p&gt;Regardless of where the playbooks are scanned, whether via 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/how-to-use-steampunk-spotter-cli-to-audit-your-playbook/"&gt;Spotter CLI&lt;/a&gt;
, 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=-PGJ09oN_PM"&gt;CI/CD&lt;/a&gt;
 or 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/spotter-and-vsc/"&gt;IDE integrations&lt;/a&gt;
, the history of all scans is available in the app, where you can track the history of each scan and observe how playbooks have improved over time. View detailed summaries of all issues, complete with descriptions, and share actual code snippets with your team to speed up troubleshooting.&lt;/p&gt;</description></item><item><title>How Deutsche Telekom MMS optimizes Ansible Playbooks with Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/how-deutsche-telekom-mms-optimizes-ansible-playbooks-with-spotter/</link><pubDate>Thu, 13 Jun 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-deutsche-telekom-mms-optimizes-ansible-playbooks-with-spotter/</guid><description>&lt;p&gt;Managing Ansible code quality across multiple teams and projects can be challenging. We talked to &lt;strong&gt;Andreas Hering, System Engineer at Deutsche Telekom MMS&lt;/strong&gt; that shared how he and his team handle the complexities of managing diverse Ansible environments with the help of Steampunk Spotter. They not only achieved significant time saving with the Spotter’s rewrite feature, but also experienced 2-4x speedup in Ansible Playbooks improvement, upgrades and maintenance compared to manual methods.&lt;/p&gt;</description></item><item><title>Steampunk Spotter 4.0: Red Hat Ansible Automation Platform integration and Windows support</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-4-0/</link><pubDate>Mon, 10 Jun 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-4-0/</guid><description>&lt;p&gt;Exciting news! Steampunk Spotter just got a major update with version 4.0. Our team has been working hard to make Spotter even better for you, and this freshly released version brings advanced enterprise features. We want to empower businesses to efficiently manage automation, ensuring safe and efficient workflows that drive collaboration, productivity, and overall success.&lt;/p&gt;
&lt;p&gt;Let’s check out the key highlights that Spotter 4.0 has in store for you.&lt;/p&gt;
&lt;h2 id="1-red-hat-ansible-automation-platform-integration"&gt;1. Red Hat Ansible Automation Platform integration&lt;/h2&gt;
&lt;p&gt;Spotter now seamlessly integrates with Ansible Automation Platform, unlocking a new level of efficiency, reliability and security in your automation.&lt;/p&gt;</description></item><item><title>Steampunk Spotter's LDAP integration</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-ldap-integration/</link><pubDate>Fri, 22 Mar 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-ldap-integration/</guid><description>&lt;p&gt;Spotter has a new enterprise integration: LDAP, including custom mapping out-of-the-box!&lt;/p&gt;
&lt;p&gt;Users of our on-premises installation are now able to sign in with their organization&amp;rsquo;s LDAP provider, massively simplifying user and permission management. In contrast to most integrations, Spotter&amp;rsquo;s LDAP integration offers no tiered limitations to functionality: if you have Spotter on-prem, you get user, group and permission mapping without having to account for an additional tier of service or support.&lt;/p&gt;</description></item><item><title>Avoid Ansible Playbooks Decay: Importance of Daily Playbook Testing</title><link>https://steampunk.si/spotter/blog/importance-of-daily-playbook-scanning/</link><pubDate>Wed, 13 Mar 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/importance-of-daily-playbook-scanning/</guid><description>&lt;p&gt;Sounds familiar? You’ve invested hours into writing a perfect Ansible Playbook only to see it fail a few months later. No matter how high-quality, super secure and reliable your playbooks are, the real challenge begins there. To maintain their functionality, consistent scanning is crucial. That may not seem like a big deal, but what if you&amp;rsquo;re dealing with thousands of playbooks? Sounds frustrating, we know. And yes, we&amp;rsquo;re here to tell you it doesn&amp;rsquo;t have to be that way.&lt;/p&gt;</description></item><item><title>Securing your automation: A guide to ensuring Ansible Playbook security</title><link>https://steampunk.si/spotter/blog/ensuring-ansible-playbook-security/</link><pubDate>Tue, 06 Feb 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ensuring-ansible-playbook-security/</guid><description>&lt;p&gt;In IT infrastructure management, automation tools like Ansible have become indispensable for streamlining workflows, reducing errors, and increasing efficiency. But, as you know, with great power comes great responsibility. In the world of automation, that means taking care of the security side of things, especially when it comes to the playbooks that make the magic happen. See how to ensure implementation of secure playbooks and enhance the overall security of your automation workflows.&lt;/p&gt;</description></item><item><title>How to assure compliance of your Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/how-to-assure-compliance-of-your-ansible-playbooks/</link><pubDate>Tue, 16 Jan 2024 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-to-assure-compliance-of-your-ansible-playbooks/</guid><description>&lt;p&gt;Compliance is a critical aspect of IT operations. It&amp;rsquo;s important to ensure that your Ansible Playbooks are compliant with all relevant regulations and standards, or your business can suffer serious consequences, reaching far beyond just technical issues. But as your infrastructure grows, it gets harder and harder to keep playbooks compliant.&lt;/p&gt;
&lt;p&gt;In this blog post we’ll explain why it’s so important and how to achieve compliance effectively and without hassle.&lt;/p&gt;</description></item><item><title>XLAB Steampunk’s Year in Review: A whole lot of (automation) magic</title><link>https://steampunk.si/blog/a-year-in-review-2023/</link><pubDate>Thu, 21 Dec 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/a-year-in-review-2023/</guid><description>&lt;p&gt;To say that the year raced by like a well-steamed machine is an understatement. No wonder, because looking back, the year was full of adventures! Join us on a trip down memory lane and celebrate our milestones.&lt;/p&gt;
&lt;h2 id="new-features"&gt;New features&lt;/h2&gt;
&lt;p&gt;In our commitment to enhancing your 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 experience, we&amp;rsquo;ve rolled out a plethora of new features:&lt;/p&gt;
&lt;p&gt;⚙️ &lt;strong&gt;Custom rules&lt;/strong&gt; - Easily create and manage custom rules, written in universal human-readable language to simplify policy management across your cloud-native stack. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=8bjzWXZC9_E&amp;amp;t=10s&amp;amp;ab_channel=XLABSteampunk"&gt;Watch DEMO.&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Ansible Playbook Development: A Step-by-step Guide</title><link>https://steampunk.si/spotter/blog/ansible-playbook-development-step-by-step-guide/</link><pubDate>Mon, 11 Dec 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ansible-playbook-development-step-by-step-guide/</guid><description>&lt;p&gt;Ansible Playbook development is the process of planning, writing, testing and maintaining the YAML files that tell Ansible what state your systems should be in. Writing a Playbook that runs is the quick part. Most of the work goes into making sure it does the right thing every time, on every host, no matter who wrote it.&lt;/p&gt;
&lt;p&gt;This guide walks through that workflow with one example from start to finish. You’ll set up a development environment and write a Playbook that configures an nginx documentation server. Then you’ll check it with ansible-lint and Steampunk Spotter, fix what they find, and run it on a test system to prove it’s idempotent.&lt;/p&gt;</description></item><item><title>Securing and streamlining your CI/CD pipelines with Jenkins and Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/secure-and-streamline-CICD-pipelines-with-jenkins-and-spotter/</link><pubDate>Fri, 24 Nov 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/secure-and-streamline-CICD-pipelines-with-jenkins-and-spotter/</guid><description>&lt;p&gt;The quickly evolving realm of software development calls for efficiency and security in continuous integration and continuous deployment (CI/CD) pipelines. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 and Jenkins are both popular DevOps tools, and they can be used together to improve the quality and security of your software development process. It is common not to deploy locally but in CI/CD pipelines in DevOps. This diminishes your control and by integrating Spotter into your Jenkins pipeline, you can automatically scan your Ansible Playbooks for errors and vulnerabilities before they are deployed to production. This can help you avoid costly and time-consuming production outages and security breaches.&lt;/p&gt;</description></item><item><title>Ansible Playbook writing for beginners: Automate your morning routine</title><link>https://steampunk.si/spotter/blog/ansible-playbooks-for-beginners-automate-daily-routine/</link><pubDate>Fri, 17 Nov 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ansible-playbooks-for-beginners-automate-daily-routine/</guid><description>&lt;p&gt;Time is precious, and while you&amp;rsquo;re undoubtedly awesome, you can&amp;rsquo;t be everywhere at once, right? Picture this: what if you could magically make some of your daily chores handle themselves? Unfortunately, we can&amp;rsquo;t wave a wand to teleport ourselves from bed to work, but there&amp;rsquo;s a bunch of tasks that can be made way easier through automation. Ansible Playbooks are a powerful tool – think of them as your minions, ready to tackle your tasks, even when you&amp;rsquo;re kicking back.&lt;/p&gt;</description></item><item><title>Steampunk Spotter 3.0: Enterprise-Grade Ansible Playbook Platform</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-3-0/</link><pubDate>Tue, 14 Nov 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-3-0/</guid><description>&lt;p&gt;In the fast-paced landscape of modern enterprise IT automation, businesses are constantly seeking solutions that enhance reliability, security, and efficiency. We’re excited to announce the release of 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter 3.0&lt;/a&gt;
, a powerful toolkit that addresses these very needs. The freshly released version unveils the Ansible Playbook Platform, a revolutionary offering set to redefine how businesses of all sizes can optimize their automation processes.&lt;/p&gt;
 &lt;figure&gt;
&lt;img alt="Steampunk Spotter dashboard and CLI scan results in the terminal" width="1579" height="888"
 src="spotter3.png"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;
&lt;p&gt;Explore what’s new.&lt;/p&gt;</description></item><item><title>Custom Policies 101: Preventing Sensitive Information Leakage in Your Playbooks</title><link>https://steampunk.si/spotter/blog/custom-policies-101-prevent-sensitive-data-leaks-in-playbooks/</link><pubDate>Tue, 24 Oct 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/custom-policies-101-prevent-sensitive-data-leaks-in-playbooks/</guid><description>&lt;p&gt;As automation takes center stage in modern IT environments, the security of automation scripts, especially Ansible Playbooks, cannot be overstated. One interesting security vulnerability in automation is keeping it compliant with company policies. This blog post will explore how to use 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
&amp;rsquo;s custom policies to prevent personally identifiable information leakage vulnerability in Ansible Playbooks. In our use case, we will demonstrate this for full name leakage prevention and be one step closer to GDPR like compliances.&lt;/p&gt;</description></item><item><title>Flexible Ansible Playbook scanning with Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/flexible-ansible-playbook-scanning-steampunk-spotter/</link><pubDate>Mon, 16 Oct 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/flexible-ansible-playbook-scanning-steampunk-spotter/</guid><description>&lt;p&gt;In the ever-evolving landscape of automation, the need for a versatile and adaptable tool is becoming increasingly vital. Enter 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
, the dynamic solution that empowers you to scan your Ansible content precisely and flexibly. &lt;strong&gt;Spotter is an Ansible Playbook Scanning platform that offers valuable insights into your playbooks to help you optimize and maximize your automation.&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;Let’s delve into the myriad of benefits Spotter brings for Ansible Playbook developers, quality assurance teams, operations teams, and security teams.&lt;/p&gt;</description></item><item><title>How to Add Spotter to Your CI/CD Process for Enhanced Security</title><link>https://steampunk.si/spotter/blog/add-spotter-to-CI-CD-process-and-enhance-security/</link><pubDate>Thu, 28 Sep 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/add-spotter-to-CI-CD-process-and-enhance-security/</guid><description>&lt;p&gt;Continuous Integration and Continuous Deployment (CI/CD) have become cornerstone practices in modern DevOps, streamlining code from development into production. However, the speed and automation of CI/CD can sometimes introduce security vulnerabilities if not handled carefully. That&amp;rsquo;s where tools like 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 come into play, serving as an added layer of security within your CI/CD pipeline.&lt;/p&gt;
&lt;h2 id="the-importance-of-code-analysis-tools-in-cicd"&gt;The Importance of Code Analysis Tools in CI/CD&lt;/h2&gt;
&lt;h3 id="challenges-in-modern-development"&gt;Challenges in Modern Development&lt;/h3&gt;
&lt;p&gt;Today’s codebases are dynamic and increasingly complex. While CI/CD pipelines facilitate rapid development, they can also introduce code vulnerabilities if there is a lack of proper analysis.&lt;/p&gt;</description></item><item><title>Steampunk Spotter: Skipping and Enforcing Checks</title><link>https://steampunk.si/spotter/blog/spotter-skipping-and-enforcing-checks/</link><pubDate>Wed, 06 Sep 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-skipping-and-enforcing-checks/</guid><description>&lt;p&gt;&lt;strong&gt;The skipping and enforcing checks feature allows you to fine-tune Spotter&amp;rsquo;s output, enabling the execution of checks that align with specific use cases.&lt;/strong&gt; For example, if Spotter finds a potential risk, which you assess and accept, you can decide to skip it and Spotter won’t show you the error, hint, or warning again. And if you are leading a team and want to be sure a certain check is always included, you can enforce it on the administrative level. &lt;strong&gt;With Spotter, you’re always in control.&lt;/strong&gt; This functionality offers &lt;strong&gt;centralized control&lt;/strong&gt; over Ansible Playbook checks, determining which checks to skip and which to enforce throughout automation workflows.&lt;/p&gt;</description></item><item><title>Using Spotter's Scan Profiles</title><link>https://steampunk.si/spotter/blog/tailored-ansible-playbook-scanning-spotter-scan-profiles/</link><pubDate>Tue, 29 Aug 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/tailored-ansible-playbook-scanning-spotter-scan-profiles/</guid><description>&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 is an Ansible Playbook Scanning platform that offers valuable insights into your playbooks to help you optimize and maximize your automation. In this blog post, we will discuss Spotter’s Scan profiles, a feature that adds a new dimension to your Ansible Playbook scanning experience. Whether you want to improve your playbook, upgrade it, or ensure it will execute securely, the scan profiles ensure that the scan results meet your specific goals.&lt;/p&gt;</description></item><item><title>AI-Powered Ansible Playbooks | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/ai-powered-ansible-playbooks/</link><pubDate>Sat, 22 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/ai-powered-ansible-playbooks/</guid><description>&lt;p&gt;While there are many AI tools that can generate Ansible Playbooks in seconds, the current state of AI systems and their knowledge base for writing playbooks is not yet sufficient to create production-ready playbooks without manual rewriting.&lt;/p&gt;
&lt;p&gt;Fortunately, we have tools such as Ansible Lint and Steampunk Spotter at our disposal to assist us in checking and iteratively improving the quality of playbooks through playbook scanning. By combining AI and Ansible Playbook scanning tools, we can speed up the playbook writing process, produce high-quality, reliable, and secure playbooks, and
enable AI tools to continuously learn from good examples, get smarter and deliver better results. With AI-powered Ansible Playbooks, we can streamline processes and transform the future of automation.&lt;/p&gt;</description></item><item><title>Improve the reliability and security of Ansible Playbooks with Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/improve-the-reliability-and-security-of-ansible-playbooks-with-spotter/</link><pubDate>Fri, 21 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/improve-the-reliability-and-security-of-ansible-playbooks-with-spotter/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.devopsmadness.com/steampunk_spotter_intro/"&gt;DevOps Madness.com&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The author of this blog post is &lt;strong&gt;Ioannis Moustakis, Solutions Architect at AWS and creator of 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.devopsmadness.com/"&gt;DevOpsMadness.com&lt;/a&gt;
 blog&lt;/strong&gt;. Opinions expressed are solely his own.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Ansible has been one of the most dominant tools for enabling configuration management and automation in complex systems. Playbooks are fundamental building blocks of Ansible as a primary way to automate a series of tasks. However, ensuring their reliability, security, quality, and effectiveness can take time, knowledge, and effort. Enter 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
, an Ansible Playbook scanning tool that helps you effortlessly create, maintain, and update Ansible Playbooks and achieve reliable and secure execution of automation. In this blog post, we’ll talk about what Spotter is, how to use it, and what benefits it brings. Let’s dive in.&lt;/p&gt;</description></item><item><title>How to automatically fix Ansible content with Steampunk Spotter</title><link>https://steampunk.si/spotter/blog/spotter-automatically-fix-ansible-content/</link><pubDate>Tue, 11 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-automatically-fix-ansible-content/</guid><description>&lt;p&gt;We&amp;rsquo;re thrilled to introduce you to one of our most exciting features - the Steampunk Spotter rewrite function. With this powerful option, Spotter can automatically fix specific errors in your Ansible Playbooks, eliminating the need for manual intervention, saving you valuable time and effort.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s walk through the automatic fix capabilities of Spotter.&lt;/p&gt;
&lt;h2 id="1-scan"&gt;1. Scan&lt;/h2&gt;
&lt;p&gt;First, let’s look at our playbook:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;--- 

- hosts: all 
 become: false 

 tasks: 

 - name: Generate a private key 
 openssl_privatekey: 
 path: &amp;amp;privkey_path /etc/nginx/ssl-nginx.key 
 size: 2048 

 - action: 
 module: file 
 mode: &amp;#39;0644&amp;#39; 
 state: present 
 delegate_to: localhost 

 - name: Create a CSR 
 openssl_csr: 
 path: &amp;amp;csr_path /etc/nginx/ssl-nginx.csr 
 privatekey_path: *privkey_path 
 commonName: &amp;#34;{{ ansible_hostname }}&amp;#34; 
 always_run: true 
 when: true 

 - name: Generate a Self Signed OpenSSL certificate 
 openssl_certificate: 
 path: &amp;amp;cert_path /etc/nginx/ssl-nginx.crt 
 provider: selfsigned 
 privatekey_path: *privkey_path 
 csr_path: *csr_path 

 - name: Template out the nginx config file 
 action: 
 module: template 
 src: &amp;#34;nginx-{{ ansible_distribution }}.conf&amp;#34; 
 dest: /etc/nginx/nginx.conf 
 mode: u=rw,g=rw,o=r 
 register: nginx_config 
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;And now, we can run the scan:&lt;/p&gt;</description></item><item><title>How to Use Steampunk Spotter in GitLab CI/CD</title><link>https://steampunk.si/spotter/blog/spotter-in-gitlab/</link><pubDate>Fri, 07 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-in-gitlab/</guid><description>&lt;p&gt;You can use 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 in many diverse ways and integrate it with your favorite tools. In this blog post, we look at how to use Spotter with GitLab CI/CD. We will demonstrate how you can use it to scan Ansible content within your GitLab repository.&lt;/p&gt;
&lt;h2 id="create-a-new-git-repository-on-gitlab"&gt;Create a new Git repository on GitLab&lt;/h2&gt;
&lt;p&gt;First, you open GitLab and create a new Git repository. To create a new project, click on &amp;ldquo;New project&amp;rdquo; and select &amp;ldquo;Create blank project,&amp;rdquo; then name the repository &amp;ldquo;spotter-gitlab-ci&amp;rdquo; and choose to initialize it with a README file while keeping it private.&lt;/p&gt;</description></item><item><title>How to Use Steampunk Spotter with GitHub Actions</title><link>https://steampunk.si/spotter/blog/spotter-github-actions/</link><pubDate>Thu, 06 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-github-actions/</guid><description>&lt;p&gt;Steampunk Spotter is a versatile tool that can be integrated with various tools to enhance your workflow. This blog post will explore using Spotter in CI/CD pipelines with GitHub Actions. By leveraging the Spotter action available on 
&lt;a target="_blank" rel="noopener noreferrer" href="https://github.com/marketplace/actions/steampunk-spotter"&gt;GitHub Marketplace&lt;/a&gt;
 we will demonstrate how to scan Ansible content within your GitHub repositories.&lt;/p&gt;
&lt;h2 id="create-a-new-git-repository-on-github"&gt;Create a new Git repository on GitHub&lt;/h2&gt;
&lt;p&gt;To begin, open GitHub and create a new Git repository.&lt;/p&gt;
 &lt;figure&gt;
&lt;img alt="Creating a new repository from the GitHub menu" width="1835" height="866"
 src="1.png"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt; 
&lt;p&gt;Give it a name like &amp;ldquo;spotter-github-ci&amp;rdquo; and ensure it is set as private. You can initialize the repository with a README file.&lt;/p&gt;</description></item><item><title>Steampunk Spotter Visual Studio Code Extension: Setup and scanning</title><link>https://steampunk.si/spotter/blog/spotter-and-vsc/</link><pubDate>Tue, 04 Jul 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-and-vsc/</guid><description>&lt;p&gt;This blog post explores the Visual Studio Code (VSC) extension of Steampunk Spotter, a powerful platform that helps you identify and fix errors in your Ansible content, making automation more reliable, secure, and effective.&lt;/p&gt;
&lt;p&gt;You can install the extension from the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://marketplace.visualstudio.com/items?itemName=xlab-steampunk.steampunk-spotter"&gt;Visual Studio Marketplace&lt;/a&gt;
 or 
&lt;a target="_blank" rel="noopener noreferrer" href="https://open-vsx.org/extension/xlab-steampunk/steampunk-spotter"&gt;Open VSX Registry.&lt;/a&gt;
 The extension requires a 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/login"&gt;Spotter user account&lt;/a&gt;
 and the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://pypi.org/project/steampunk-spotter/"&gt;Spotter CLI&lt;/a&gt;
 installed in the console that you use with VS Code by default.&lt;/p&gt;</description></item><item><title>How to use Steampunk Spotter CLI to scan your Ansible Playbook</title><link>https://steampunk.si/spotter/blog/how-to-use-steampunk-spotter-cli-to-audit-your-playbook/</link><pubDate>Mon, 26 Jun 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-to-use-steampunk-spotter-cli-to-audit-your-playbook/</guid><description>&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
 helps you simplify and accelerate your automation with improved playbooks that guarantee reliable execution. The Steampunk Spotter CLI enables use from the console with the ability to scan Ansible content such as playbooks, roles, collections, or task files.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s get started!&lt;/p&gt;
&lt;h2 id="step-1-install-steampunk-spotter"&gt;Step 1: Install Steampunk Spotter&lt;/h2&gt;
&lt;p&gt;To use Steampunk Spotter CLI, you first need to sign up 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/register/team-plan"&gt;here.&lt;/a&gt;
 By signing up, we avoid unauthenticated requests and reduce the API’s malicious load while making it easily accessible.&lt;/p&gt;</description></item><item><title>Managing infrastructure using Ansible Automation Platform</title><link>https://steampunk.si/blog/managing-infrastructure-using-ansible-tower/</link><pubDate>Thu, 22 Jun 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/managing-infrastructure-using-ansible-tower/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on September 22, 2020. The content has been updated to reflect the latest releases.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Some of our 
&lt;a target="_self" href="https://steampunk.si/blog/aws-ansible-collection-vpc-getting-started/" title="Getting started with IPv4 for Amazon VPC" &gt;previous&lt;/a&gt;
 
&lt;a target="_self" href="https://steampunk.si/blog/enforcing-compliance-using-aws-ansible-collection/" title="Enforcing Compliance using the AWS Ansible Collection" &gt;posts&lt;/a&gt;
 focused on infrastructure management
using Ansible. We will take things one step further today and create a
rudimentary self-service catalog using 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/products/automation-platform" title="Red Hat Automation platform home page" &gt;Ansible Automation Platform&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Speed up Playbook Development: Assisted Playbook Writing Feature</title><link>https://steampunk.si/spotter/blog/ansible-playbooks-steampunk-spotter-assisted-writing/</link><pubDate>Thu, 08 Jun 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ansible-playbooks-steampunk-spotter-assisted-writing/</guid><description>&lt;p&gt;In today&amp;rsquo;s fast-paced world of automation, efficiency is key. Simplifying and speeding up playbook writing can significantly maximize productivity and help you achieve automation goals. That&amp;rsquo;s why we are excited to introduce Spotter&amp;rsquo;s Assisted Playbook Writing feature. In this blog post, we will delve into the powerful capabilities of Spotter and how it transforms how you create playbooks.&lt;/p&gt;
&lt;p&gt;The feature is available in Steampunk Spotter’s Visual Studio Code extension. You can install the extension from the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://marketplace.visualstudio.com/items?itemName=xlab-steampunk.steampunk-spotter"&gt;Visual Studio Marketplace&lt;/a&gt;
 or 
&lt;a target="_blank" rel="noopener noreferrer" href="https://open-vsx.org/extension/xlab-steampunk/steampunk-spotter"&gt;Open VSX Registry.&lt;/a&gt;
 The extension requires a 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/login"&gt;Steampunk Spotter&lt;/a&gt;
 user account and the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://pypi.org/project/steampunk-spotter/"&gt;Steampunk Spotter CLI&lt;/a&gt;
 installed in the console that you use with VS Code by default.&lt;/p&gt;</description></item><item><title>Check out the checks in Spotter</title><link>https://steampunk.si/spotter/blog/checks-in-spotter-and-our-roadmap/</link><pubDate>Mon, 05 Jun 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/checks-in-spotter-and-our-roadmap/</guid><description>&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter,&lt;/a&gt;
 an Ansible Playbook Platform, includes a variety of checks that improve the quality, reliability, and security of your Ansible Playbooks. The checks are divided into several categories:  &lt;/p&gt;
&lt;h2 id="best-practice-checks"&gt;Best practice checks&lt;/h2&gt;
&lt;p&gt;Best practice checks help you write playbooks that keep a common standard and aim to be more consistent, reliable, and readable. They also support the Red Hat Ansible Best Practice guide.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Check for fully qualified collection names (FQCN) and automatically apply rewrites.&lt;/p&gt;</description></item><item><title>Steampunk Spotter: What's new in 2.0?</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-2-0/</link><pubDate>Thu, 01 Jun 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-2-0/</guid><description>&lt;p&gt;We’re excited to announce that Spotter 2.0 is here, bigger and better, ready to conquer all of your automation challenges! Our dedicated team has once again outdone themselves and gone the extra mile to ensure the stability, reliability, and security of your Ansible Playbooks. The freshly released version is packed with new and enhanced enterprise-ready features and checks that will make your automation even more reliable and secure. Explore what’s new.&lt;/p&gt;</description></item><item><title>How Spotter helps Systems Architects reach trustable automation</title><link>https://steampunk.si/spotter/blog/how-spotter-helps-systems-architects-reach-trustable-automation/</link><pubDate>Tue, 09 May 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-spotter-helps-systems-architects-reach-trustable-automation/</guid><description>&lt;p&gt;We talked with Sebastian Gumprich, a Systems Architect and DevOps enthusiast, who was one of the
first early adopters of Steampunk Spotter and provided us with valuable insights for
improvements.&lt;/p&gt;
&lt;p&gt;Sebastian works at Telekom MMS GmbH, which offers a broad scope of IT services to its customers.
In his role within the operations department, which provides infrastructure, management and
hosting of customer’s applications, Sebastian is responsible for developing solutions to improve
and automate the work of all operations teams. The company relies heavily on automation,
especially Red Hat Ansible, to ensure the best possible quality of services.&lt;/p&gt;</description></item><item><title>Join us for Red Hat Summit and see Spotter in action</title><link>https://steampunk.si/spotter/blog/join-us-for-red-hat-summit-and-see-spotter-in-action/</link><pubDate>Tue, 25 Apr 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/join-us-for-red-hat-summit-and-see-spotter-in-action/</guid><description>&lt;p&gt;Good news! We don’t have to wait until fall for the greatest IT automation event of them all. This year, AnsibleFest will be part of 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.redhat.com/en/summit"&gt;Red Hat Summit, the premier open-source technology event&lt;/a&gt;
 and it&amp;rsquo;s only a month away. From May 23 – 25, Ansible enthusiasts from around the world will crowd Boston in search of exciting automation experience!&lt;/p&gt;
&lt;p&gt;With a diverse lineup of live sessions, keynotes, hands-on labs, and partner programming, Red Hat Summit promises to cater to everyone’s interest and enable attendees to stay up-to-date on the latest trends in the field of open source, hybrid cloud, and automation.&lt;/p&gt;</description></item><item><title>Custom policies: Achieve secure and compliant automation</title><link>https://steampunk.si/spotter/blog/spotter-custom-policies/</link><pubDate>Fri, 14 Apr 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/spotter-custom-policies/</guid><description>&lt;p&gt;Let’s face it, what it means to have successful automation varies from one business to another. At 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk Spotter&lt;/a&gt;
, we are acutely aware of this fact. We heard you loud and clear, custom policies are here, available as an enterprise feature. They allow you to create new Spotter checks according to specific policies you might be using, either for yourself or your clients. By using custom policies, you can be sure your Ansible Playbooks act according to all internal or general regulatory standards that you set for yourself.&lt;/p&gt;</description></item><item><title>Ansible vs Jenkins: Main differences and which one to choose?</title><link>https://steampunk.si/spotter/blog/ansible-vs-jenkins/</link><pubDate>Tue, 04 Apr 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ansible-vs-jenkins/</guid><description>&lt;p&gt;Ansible and Jenkins are popular, well-acclaimed automation tools used to implement DevOps principles. Can, or better yet, should they be compared? Let’s find out!&lt;/p&gt;
&lt;p&gt;Ansible is used for various automation applications like cloud provisioning, configuration management, and intra-service orchestration, while Jenkins simplifies application development and deployment, used for building, testing, and deploying software projects.&lt;/p&gt;
&lt;p&gt;Often used in the Jenkins pipeline flow, Ansible can be used for reusing roles and playbooks to provision target environments. Jenkins can be the orchestrator instead of the executor for shell scripts this way. Ansible shines at resource orchestration and software provisioning, whereas Jenkins shines at CI/CD deployment and plugins. Though the two tools are basically DevOps tools, they have many differences in terms of features and functionalities. They can, however, also complement each other.&lt;/p&gt;</description></item><item><title>Official information about Steampunk Spotter</title><link>https://steampunk.si/spotter/ai-info-page/</link><pubDate>Thu, 23 Mar 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/ai-info-page/</guid><description>Shift-left governance for AI-generated Ansible and Terraform code. Deterministic policy, CIS, CVE and supply chain checks before anything runs.</description></item><item><title>Ansible Automation Platform 2 Upgrade: Preparation and Planning</title><link>https://steampunk.si/spotter/blog/aap2-upgrade-preparation-and-planning/</link><pubDate>Wed, 15 Mar 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/aap2-upgrade-preparation-and-planning/</guid><description>&lt;p&gt;Every day we are edging closer and closer to finally migrating to 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/upgrade-to-ansible-platform-2/?utm_source=aap2-preparation-post&amp;amp;utm_medium=blog"&gt;Ansible Automation Platform 2&lt;/a&gt;
 (AAP 2). It brings updated architecture, new tools, and an enhanced automation experience that will simplify and modernize your automation journey. Now the time has come to start thoroughly preparing for the upgrade. We are going to talk about how to prepare for AAP 2.3 (the latest released version) update and be ahead of the curve when the day finally comes.&lt;/p&gt;</description></item><item><title>Client Spotlight: Scale Computing accelerates customer adoption with Ansible integration</title><link>https://steampunk.si/blog/scale-computing-accelerates-customer-adoption-with-ansible-integration/</link><pubDate>Tue, 14 Mar 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/scale-computing-accelerates-customer-adoption-with-ansible-integration/</guid><description>&lt;p&gt;To enable its customers to remotely deploy applications to multiple sites simultaneously, Scale Computing decided to enhance its product with Ansible integration. To achieve the best possible result, they decided to trust XLAB Steampunk to develop the Ansible Collection. Did we live up to their expectations and help them achieve desired outcomes? What was it like working with us?&lt;/p&gt;
&lt;p&gt;In today’s client spotlight, we talk to Dave Demlow, Vice President of product strategy at Scale Computing.&lt;/p&gt;</description></item><item><title>How to create a reliable Ansible Playbook (with a template)</title><link>https://steampunk.si/spotter/blog/how-to-create-a-reliable-ansible-playbook/</link><pubDate>Mon, 06 Mar 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/how-to-create-a-reliable-ansible-playbook/</guid><description>&lt;p&gt;So, you decided to write your first Ansible Playbook. Maybe not even your first, maybe you just want to know how to write secure and reliable ones. Splendid, you came to the right place. This blog is a simple guide to help you get started or improve on your playbook writing journey.&lt;/p&gt;
&lt;h2 id="what-can-you-do-with-ansible-playbooks"&gt;What can you do with Ansible Playbooks?&lt;/h2&gt;
&lt;p&gt;The whole point of writing playbooks is to automate those pesky tedious manual tasks. In general, automation usually applies to larger systems of IT infrastructure, so we assume you would like to create a reusable configuration management and multi machine
deployment system. This system should be simple, yet capable of deploying complex applications easily. High quality Ansible Collections can help you establish this robust automation workflow, but their content needs to be then applied appropriately, to achieve the
key needed ingredient of great automation, which is their reliability.&lt;/p&gt;</description></item><item><title>Client Spotlight: One of Slovenia's largest Financial Services Companies automated infrastructure with Ansible</title><link>https://steampunk.si/blog/slovenia-largest-financial-services-companies-automated-infrastructure-with-ansible/</link><pubDate>Tue, 14 Feb 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/slovenia-largest-financial-services-companies-automated-infrastructure-with-ansible/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;One of Slovenia&amp;rsquo;s largest financial services companies
needed a solution to automate the management of its
infrastructure. With a proof of concept, XLAB implemented
production-ready deployment of Red Hat Ansible Automation
Platform, helping the client take the first step on its
path to efficient and transparent IT infrastructure
management.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-challenge"&gt;The Challenge&lt;/h2&gt;
&lt;p&gt;The client used various automation tools that were vendor-specific or even did things manually, especially when it came to Linux. While they managed Windows servers sufficiently, the situation with Linux servers was a bit different. They have never systematically tackled centralized management of Linux servers. They were looking for a solution to unify the automation of their infrastructure. Another major challenge was ensuring compliance, since as a financial services company they are subject to constant internal and external audits.&lt;/p&gt;</description></item><item><title>Future of Ansible Playbook writing: How ChatGPT is changing the game</title><link>https://steampunk.si/spotter/blog/chat-GPT-ansible-playbooks/</link><pubDate>Tue, 31 Jan 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/chat-GPT-ansible-playbooks/</guid><description>&lt;p&gt;In the past few months, AI systems have caused quite a stir on the web. We couldn&amp;rsquo;t wait to get our hands dirty and try to write Ansible Playbooks even faster, or at least learn something new. In this post, we&amp;rsquo;ll take a look at the new AI trends seen around the IT world and we&amp;rsquo;ll test how we can use AI to create playbooks.&lt;/p&gt;
&lt;p&gt;Or as ChatGPT would say, &amp;ldquo;Welcome to the wonderful world of AI! It&amp;rsquo;s like the Wild West of technology, where the robots are the sheriffs, and the algorithms are the outlaws. In this post, we&amp;rsquo;ll be taming the AI beast and teaching it to do our bidding.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Upgrade to Ansible Automation Platform 2: What's new and how to speed up the migration</title><link>https://steampunk.si/spotter/blog/upgrade-to-ansible-platform-2/</link><pubDate>Thu, 26 Jan 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/upgrade-to-ansible-platform-2/</guid><description>&lt;p&gt;Red Hat launched Ansible Automation Platform 2 (AAP2) in September 2021 and has since already updated to version 2.3. It brings
many excellent features to further enhance your automation. The current date to finally upgrade from Ansible Automation
Platform 1.2 to AAP2 is September 2023, so now would be a great time to start thinking about the upgrade.&lt;/p&gt;
&lt;p&gt;Yes, we know that upgrades can present a challenge, but do not let it hold you back. Not only do the benefits of AAP2 far
outweigh any difficulties you may face, with the help of the right tools, such as 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/?utm_source=AAP2&amp;amp;utm_medium=blog"&gt;Steampunk Spotter&lt;/a&gt;
, you can upgrade
your playbooks in minutes instead of hours.&lt;/p&gt;</description></item><item><title>Is Ansible Lint enough? How to build on it for production-ready playbooks</title><link>https://steampunk.si/spotter/blog/why-use-steampunk-spotter-when-we-have-ansible-lint/</link><pubDate>Tue, 24 Jan 2023 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/why-use-steampunk-spotter-when-we-have-ansible-lint/</guid><description>&lt;p&gt;&lt;strong&gt;Ansible Lint&lt;/strong&gt; is a tool that checks your Ansible Playbooks for errors and suggests improvements. &lt;strong&gt;Steampunk Spotter&lt;/strong&gt; checks them too, and then goes further: it enforces your organization’s policy on every change before it reaches production. So, is Ansible Lint enough? Is Spotter just a fancy linter? What does Spotter have that Ansible Lint doesn’t already?&lt;/p&gt;
&lt;p&gt;We hear these questions a lot, and we understand them. At first glance, the two tools look similar. The real answer is that they &lt;strong&gt;complement each other&lt;/strong&gt;. Ansible Lint keeps your code clean and consistent, and it’s always the right place to start. Spotter picks up where Ansible Lint leaves off. It’s a governance layer for your automation code that checks every change against your policy, including AI-generated code.&lt;/p&gt;</description></item><item><title>Step by step analysis of an Ansible Upgrade</title><link>https://steampunk.si/spotter/webinars-training/step-by-step-analysis-of-ansible-upgrade/</link><pubDate>Wed, 07 Dec 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/step-by-step-analysis-of-ansible-upgrade/</guid><description>&lt;p&gt;Upgrading Ansible Playbooks to the newest Ansible version can be quite a challenge,
as a lot can change between versions (best practices alter, parameters and modules are moved or renamed,
attributes are deprecated). And if you&amp;rsquo;re upgrading from older versions when Ansible Collections weren&amp;rsquo;t even a thing,
you&amp;rsquo;re in for some heavy lifting if you approach this process manually.&lt;/p&gt;
&lt;p&gt;In this webinar, we take you through the process of upgrading your playbooks from Ansible 2.4 to Ansible 2.14
step by step and we show you how Steampunk Spotter can help you fix five years of dependency changes in no time.&lt;/p&gt;</description></item><item><title>Automate and strengthen your security with Ansible</title><link>https://steampunk.si/blog/automate-and-strengthen-your-security-with-ansible/</link><pubDate>Thu, 17 Nov 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/automate-and-strengthen-your-security-with-ansible/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.xlab.si/blog/automate-and-strengthen-your-security-with-ansible/"&gt;XLAB Blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Modern IT systems and infrastructures are becoming increasingly complex, and while
technological advancements bring many benefits to organizations, they also open up
new opportunities to exploit their security vulnerabilities and weaknesses. The
consequences of sophisticated cyber attacks can be severe, ranging from financial
losses and lost productivity to legal liability and reputational damage, so
security of IT infrastructure should be among the company’s priorities. And while
this is not an easy task, it is definitely one that companies must address to
ensure the security of their business.&lt;/p&gt;</description></item><item><title>Keeping your secrets out of Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/aws-credentials-safety/</link><pubDate>Thu, 10 Nov 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/aws-credentials-safety/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on July 15, 2020, but the content has since been updated to adhere to latest best practices.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Every good web service needs a good authentication layer. AWS uses IAM
to manage users, one of which is your development user (you&amp;rsquo;re not using the
root account, are you?). How do we authenticate with AWS when Ansible? Let&amp;rsquo;s find out!&lt;/p&gt;</description></item><item><title>Steampunk Spotter: Analyze Ansible Playbooks and Enhance Automation</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-analyze-ansible-playbooks-enhance-automation/</link><pubDate>Wed, 09 Nov 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-analyze-ansible-playbooks-enhance-automation/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on October 13, 2022. The content has been updated to reflect the latest releases.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Don&amp;rsquo;t you wish you had a little helper by your side to spot elusive errors when writing Ansible Playbooks? Or anticipate potential problems playbooks might cause when you run them? Well, now you do!&lt;/p&gt;
&lt;p&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;&lt;strong&gt;Steampunk Spotter&lt;/strong&gt;&lt;/a&gt;
 is a &lt;strong&gt;powerful platform you can use to analyze and enhance your Ansible Playbooks.&lt;/strong&gt; It helps you simplify and speed up your automation with improved &lt;strong&gt;playbooks that guarantee reliable execution.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Steampunk Spotter: What's new in 1.1?</title><link>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-1-1/</link><pubDate>Thu, 03 Nov 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/steampunk-spotter-what-is-new-in-1-1/</guid><description>&lt;p&gt;We&amp;rsquo;re constantly improving Steampunk Spotter by adding new checks that enhance
stability, reliability, and security of your Ansible Playbooks, and enriching the
Spotter app with advanced reporting features. We&amp;rsquo;re excited to announce the release
of version 1.1 of Spotter, which brings new checks for an easier Ansible upgrade
process, new integration, and a new reporting feature in the Spotter app, among
other improvements. Read on to learn what&amp;rsquo;s new in Spotter 1.1.&lt;/p&gt;</description></item><item><title>Introduction to configuration management tools</title><link>https://steampunk.si/blog/introduction-to-configuration-management-tools/</link><pubDate>Wed, 12 Oct 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/introduction-to-configuration-management-tools/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally posted on October, 22, 2020. The content has been revised to reflect latest trends.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In this article, you&amp;rsquo;ll learn the basics of Configuration Management tools so
that you can decide which one you need. Whether you&amp;rsquo;re looking to automate
your infrastructure management or are just browsing for future reference,
you&amp;rsquo;ll walk away with a handful of useful takeaways and insights.&lt;/p&gt;</description></item><item><title>Getting started with Ansible</title><link>https://steampunk.si/blog/getting-started-with-ansible/</link><pubDate>Fri, 07 Oct 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/getting-started-with-ansible/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on November 12, 2020, but the content has been updated according to the recent Ansible changes.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In our 
&lt;a target="_self" href="https://steampunk.si/blog/introduction-to-configuration-management-tools/" title="Introduction to tonfiguration management tools post" &gt;previous blog post&lt;/a&gt;
, we looked at what configuration management
tools bring to the table. And in this post, we will take a closer look at
Ansible, our configuration management tool of choice. So if you want to learn
what Ansible is, what it does, and how it works, this is the post for you.&lt;/p&gt;</description></item><item><title>The Best Cloud Infrastructure Automation Tools of 2022</title><link>https://steampunk.si/blog/four-best-cloud-infrastructure-automation-tools-2021/</link><pubDate>Fri, 07 Oct 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/four-best-cloud-infrastructure-automation-tools-2021/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on March 18, 2021, but the content has been updated according to the recent trends.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Cloud automation tools can save companies time and money by enabling them to
focus their efforts and resources on value-added activities instead of managing
their cloud infrastructure. And as a cloud provider, it is in your best
interest to ensure your users have the best possible experience by automating
at scale.&lt;/p&gt;</description></item><item><title>Join us for AnsibleFest and Contributor Summit 2022</title><link>https://steampunk.si/blog/join-us-for-ansiblefest-2022/</link><pubDate>Fri, 30 Sep 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/join-us-for-ansiblefest-2022/</guid><description>&lt;p&gt;Are you ready for one of the biggest IT automation events of the year? In less than
a month, Ansible enthusiasts from around the world will gather for AnsibleFest.
This year’s event will feature a wide range of live sessions, labs, demos, and also
on-demand sessions, so everyone is sure to find something interesting, catch up on
the latest news, and expand their Ansible knowledge.&lt;/p&gt;
&lt;p&gt;And there’s no better way to warm up before the big event than to attend the
Ansible Contributor Summit, which takes place the day before AnsibleFest. It is a
great opportunity to get involved in the Ansible community, find out how it works,
and get a glimpse of future plans.&lt;/p&gt;</description></item><item><title>Steampunk Spotter</title><link/><pubDate>Tue, 20 Sep 2022 00:00:00 +0000</pubDate><guid/><description>&lt;p&gt;Steampunk Spotter analyzes and provides recommendations for your Ansible Playbooks to help you increase the reliability
and security of your automation.&lt;/p&gt;</description></item><item><title>Dealing with Ansible upgrades in an intelligent way</title><link>https://steampunk.si/spotter/blog/dealing-with-ansible-upgrades-in-an-intelligent-way/</link><pubDate>Wed, 07 Sep 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/dealing-with-ansible-upgrades-in-an-intelligent-way/</guid><description>&lt;p&gt;If you are reading this, you are no stranger to the Ansible update and upgrade process. The fact that Ansible is constantly being improved is great. And while the community is making its best effort to minimize breaking changes, there are times when keeping your Ansible content up to date requires additional work. To make things as clear as possible, let&amp;rsquo;s tackle this topic step by step.&lt;/p&gt;
&lt;p&gt;In this post, we&amp;rsquo;ll explain:&lt;/p&gt;</description></item><item><title>Say hello to Steampunk Spotter: Assisted Automation Writing Tool</title><link>https://steampunk.si/spotter/blog/say-hello-to-steampunk-spotter/</link><pubDate>Tue, 30 Aug 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/say-hello-to-steampunk-spotter/</guid><description>&lt;p&gt;There hasn’t been much buzz around our Ansible Playbook Quality Scanner lately. But with a good reason. Our team has been putting blood, sweat, and tears (of
joy 😉) into shaping the Scanner into what it was meant to be all along - the ultimate helper for your automation.&lt;/p&gt;
&lt;p&gt;With a bunch of new checks and features added, Scanner actually grew so much, it outgrew its name. It evolved into 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;&lt;strong&gt;Steampunk Spotter&lt;/strong&gt;&lt;/a&gt;
, indispensable tool that
analyzes and enhances your Ansible Playbooks to help you reduce risks and speed up your automation.&lt;/p&gt;</description></item><item><title>Automating management of Linux infrastructure with Ansible</title><link>https://steampunk.si/blog/automating-management-of-linux-infrastructure-with-ansible/</link><pubDate>Wed, 03 Aug 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/automating-management-of-linux-infrastructure-with-ansible/</guid><description>&lt;p&gt;Ansible can be used to automate anything, 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/why-choose-ansible-for-it-automation/" title="Why choose Ansible?" &gt;from configuration management, application deployment, provisioning, orchestration, and networking to security.&lt;/a&gt;
 In this post, we will focus on one specific use case: setting up and updating Linux
with Ansible.&lt;/p&gt;
&lt;h2 id="problem"&gt;Problem&lt;/h2&gt;
&lt;p&gt;Our client needed help with optimizing the management of their server fleet. The
existing environment consists of a Microsoft Active Directory (AD) domain with
Windows and Linux servers. The network is isolated. There is no connection to the
Internet except for a few select services. For example, operating system updates
are retrieved from the Internet but by a single dedicated server acting as an
application-level firewall and a caching proxy.&lt;/p&gt;</description></item><item><title>Ansible Playbook Best Practices: How to Write High-Quality Playbooks</title><link>https://steampunk.si/spotter/blog/ultimate-guide-for-high-quality-ansible-playbooks/</link><pubDate>Wed, 13 Jul 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/ultimate-guide-for-high-quality-ansible-playbooks/</guid><description>&lt;p&gt;Most failed Ansible runs trace back to a few habits: a messy project structure, tasks that don’t enforce a state, secrets stored in plain text, and code that reached production without being tested. The Ansible playbook best practices below fix those habits, and each one comes with a YAML example you can adapt.&lt;/p&gt;
&lt;p&gt;We’ve written countless Ansible Playbooks and Ansible Collections, and this guide collects what we’ve learned along the way. It covers project layout, readable tasks, idempotency, variables, testing, security and reviewing AI-generated code.&lt;/p&gt;</description></item><item><title>What we learned about IT automation at Red Hat Summit 2022</title><link>https://steampunk.si/blog/what-we-learned-at-red-hat-summit/</link><pubDate>Thu, 02 Jun 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/what-we-learned-at-red-hat-summit/</guid><description>&lt;p&gt;How often do you get the chance to hear firsthand from the people behind the code? Red Hat Summit, the premier open source technology event, brings a valuable opportunity to listen to open source leaders and the community, hear the latest news and announcements, and learn more about 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/the-benefits-of-it-automation-and-why-you-should-start-using-it-now/" title="The benefits of IT automation" &gt;IT automation and Ansible&lt;/a&gt;
.&lt;/p&gt;
&lt;p&gt;Whether you are just learning about automation or want to catch up on the latest
Ansible trends, everyone can find something at the Summit. The event took place on
May 10 and 11, but don’t worry if you missed it – most of the sessions are still
available on-demand, so you can watch them whenever you want (while we all
impatiently wait for AnsibleFest, where all IT automation enthusiasts really get
our kicks off). We have prepared a brief summary of our favourites, so keep
reading.&lt;/p&gt;</description></item><item><title>Why choose Ansible for your IT automation</title><link>https://steampunk.si/blog/why-choose-ansible-for-it-automation/</link><pubDate>Tue, 26 Apr 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/why-choose-ansible-for-it-automation/</guid><description>&lt;p&gt;Increasing infrastructure complexity and limited time and staff – IT teams not yet embracing automation struggle to keep the vital IT processes up and
running. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/it-automation-ignites-business-growth/" title="IT automation ignites business growth" &gt;IT automation increases productivity and efficiency while relieving teams of manual tasks, minimizing service disruptions and the risk of errors.&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;You know manually keeping up isn&amp;rsquo;t working anymore and you know the benefits of automation. But what now? Before tackling the deployment of automation across
your IT infrastructure, you first need to choose the appropriate tool, capable of solving your challenges most efficiently. Yes, there are many automation
tools out there, but one stands out. Read on to see why choose Red Hat Ansible and what you can automate with it.&lt;/p&gt;</description></item><item><title>Technical workshop: Automation with Ansible</title><link>https://steampunk.si/blog/automation-with-ansible-workshop/</link><pubDate>Thu, 14 Apr 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/automation-with-ansible-workshop/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.xlab.si/blog/technical-workshop-automation-with-ansible/" title="Original post" &gt;XLAB blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Managing dynamic IT environments is no longer possible without IT automation, which frees IT teams from repetitive tasks, increases productivity and efficiency, reduces the chance of errors, and 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.xlab.si/blog/do-more-faster-it-automation-ignites-business-growth/" title="IT automation ignites business growth" &gt;allows you to do much more with the resources you have&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Do more, faster: IT automation ignites business growth</title><link>https://steampunk.si/blog/it-automation-ignites-business-growth/</link><pubDate>Thu, 10 Mar 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/it-automation-ignites-business-growth/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.xlab.si/blog/do-more-faster-it-automation-ignites-business-growth/" title="Original post" &gt;XLAB blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Modern businesses must respond quickly to the rapidly evolving technology landscape and market demands and
innovate faster than ever before to deliver top-notch services, providing superior user experience.
That can&amp;rsquo;t be done without constantly incorporating new technologies. And as the world moves forward at the speed of light, IT teams -
the backbone of modern organizations - struggle to keep the lights on when they should be shining instead.&lt;/p&gt;</description></item><item><title>Avoiding common mistakes in your Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/avoiding-common-mistakes-ansible-playbooks/</link><pubDate>Wed, 12 Jan 2022 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/avoiding-common-mistakes-ansible-playbooks/</guid><description>&lt;p&gt;Ansible Collections gave us much more control over the content we use when building our Ansible
Playbooks. But they also brought on a new challenge: identifying high-quality content. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/five-tips-for-choosing-an-ansible-collection/" title="5 tips for choosing an Ansible Collection" &gt;Take a look here to see how to make sure the content you intend to use in your playbooks is up to standard.&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Avoiding common mistakes in Ansible Playbooks | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/avoiding-common-mistakes-ansible-playbooks/</link><pubDate>Tue, 07 Dec 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/avoiding-common-mistakes-ansible-playbooks/</guid><description>&lt;p&gt;When we write an Ansible Playbook or role, we usually do so because we want to automate error-prone manual tasks.
But if the Ansible Playbook we wrote is unreliable, all we did is replace one source of problems with another. Fortunately,
with a little bit of knowledge, discipline, and help from appropriate tools, everyone can write a high-quality Ansible Playbook.&lt;/p&gt;
&lt;p&gt;In this webinar, you’ll learn how to make your Ansible Playbooks reliable and versatile and get familiar with the tools you can use to
improve the quality of your playbooks, such as our Ansible Playbook Quality Scanner. As a bonus, you’ll get answers from a developer
involved in maintaining the Molecule and Ansible Lint tools.&lt;/p&gt;</description></item><item><title>Cloud automation for cloud providers | XLAB Steampunk</title><link>https://steampunk.si/webinars-training/cloud-automation-for-cloud-providers/</link><pubDate>Tue, 07 Dec 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/webinars-training/cloud-automation-for-cloud-providers/</guid><description>&lt;p&gt;Why should cloud providers care about Ansible integrations?
Because having a high-quality Ansible Collection for your cloud gives your users the ability to manage their infrastructure with ease,
and the improved user experience accelerates the adoption of your cloud in return.&lt;/p&gt;
&lt;p&gt;In this webinar, you&amp;rsquo;ll find out more about the value the Red Hat Ansible Automation Platform brings to you and your users.
You&amp;rsquo;ll also learn how XLAB Steampunk experts can help you get to market faster, automate your customers&amp;rsquo; complex tasks,
and increase revenue - all without having to build your own Ansible practice.&lt;/p&gt;</description></item><item><title>Using Steampunk Scanner's Command Line Interface (CLI)</title><link>https://steampunk.si/spotter/blog/using-steampunk-scanners-command-line-interface/</link><pubDate>Thu, 11 Nov 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/using-steampunk-scanners-command-line-interface/</guid><description>&lt;p&gt;Almost exactly five months ago, we unveiled the first version of 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/"&gt;Steampunk
Scanner&lt;/a&gt;
. To keep things simple, we only offered an online version at that
time. The initial version took an Ansible Playbook as input and returned some
suggestions on how to 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/writing-reliable-ansible-playbooks/" title="Blog post about writing reliable playbooks" &gt;improve your content&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>What's new: Automating ServiceNow with Ansible Automation Platform</title><link>https://steampunk.si/blog/what-is-new-automating-servicenow-with-ansible-automation-platform/</link><pubDate>Wed, 13 Oct 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/what-is-new-automating-servicenow-with-ansible-automation-platform/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/whats-new-automating-servicenow-with-ansible-automation-platform" title="Original blog post" &gt;Ansible blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;It has been almost half a year since the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/" title="XLAB Steampunk home page" &gt;XLAB Steampunk&lt;/a&gt;
 and Red Hat Ansible
Automation Platform teams developed the first version of the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/ansible-collections/servicenow/" title="Basic information about the ServiceNow Ansible Collection" &gt;Red Hat Ansible
Certified Content Collection for ServiceNow IT Service Management
(ITSM)&lt;/a&gt;
. You may also want to read our 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/certified-collection-servicenow" title="Introduction to managing ServiceNow using Ansible" &gt;ServiceNow introduction&lt;/a&gt;
 if you
are not familiar with this already. So, let’s take a look at what is new since
the last release.&lt;/p&gt;</description></item><item><title>Did you miss our AnsibleFest talks? Watch them on demand!</title><link>https://steampunk.si/blog/ansiblefest-2021-talks-on-demand/</link><pubDate>Mon, 04 Oct 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansiblefest-2021-talks-on-demand/</guid><description>&lt;p&gt;AnsibleFest, the event all of us IT automation enthusiasts look forward to all
year, is behind us. We&amp;rsquo;re proud to have once again been an active part of this
invaluable opportunity to catch up on the latest news and expand Ansible
skills, as we are always happy to share our Ansible expertise and help make
your automation journey smoother.&lt;/p&gt;</description></item><item><title>Join us for AnsibleFest and Contributor Summit 2021</title><link>https://steampunk.si/blog/join-us-for-ansiblefest-2021/</link><pubDate>Wed, 22 Sep 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/join-us-for-ansiblefest-2021/</guid><description>&lt;p&gt;September holds a special place in the Ansible world. Why? Because of the

&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/ansiblefest" title="AnsibleFest 2021 home page" &gt;AnsibleFest&lt;/a&gt;
, of course! It is one of the biggest IT automation events in
the world where seasoned pros and new Ansible enthusiasts alike can find
something exciting to learn.&lt;/p&gt;</description></item><item><title>WEBINAR for cloud providers: Cloud automation with Ansible</title><link>https://steampunk.si/blog/webinar-for-cloud-providers-cloud-automation-with-ansible/</link><pubDate>Thu, 26 Aug 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/webinar-for-cloud-providers-cloud-automation-with-ansible/</guid><description>&lt;p&gt;Ansible can automate anything, and cloud is no exception. Automating cloud with
Ansible gives your users a chance to simplify management of their existing
infrastructure. And when your users benefit, you benefit, too!&lt;/p&gt;</description></item><item><title>Writing reliable Ansible Playbooks</title><link>https://steampunk.si/spotter/blog/writing-reliable-ansible-playbooks/</link><pubDate>Thu, 17 Jun 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/blog/writing-reliable-ansible-playbooks/</guid><description>&lt;p&gt;We often talk about 
&lt;a target="_self" href="https://steampunk.si/blog/ansible-role-argument-specification/"&gt;techniques and tools&lt;/a&gt;
 that help developers write
high-quality Ansible content (modules and plugins). Of course, having

&lt;a target="_self" href="https://steampunk.si/blog/five-tips-for-choosing-an-ansible-collection/"&gt;high-quality Ansible collections&lt;/a&gt;
 is a prerequisite for creating robust
automation workflows, but Ansible Playbook authors still need to use that
content appropriately. And this is the topic we will talk about today.&lt;/p&gt;</description></item><item><title>Cloud automation with Ansible series: Inventory caching</title><link>https://steampunk.si/blog/cloud-automation-with-ansible-series-inventory-caching/</link><pubDate>Thu, 03 Jun 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/cloud-automation-with-ansible-series-inventory-caching/</guid><description>&lt;p&gt;We&amp;rsquo;ve previously talked about 
&lt;a target="_self" href="https://steampunk.si/blog/cloud-automation-with-ansible-series-dynamic-inventory/" title="Using a dynamic inventory for cloud automation with Ansible." &gt;using a dynamic inventory for cloud automation with Ansible&lt;/a&gt;

and promised to also explore inventory caching.
Here we are!
We&amp;rsquo;re looking at what inventory caching is, why we need it, and how it can speed up our day-to-day operations
with Ansible.&lt;/p&gt;</description></item><item><title>Ansible role argument specification</title><link>https://steampunk.si/blog/ansible-role-argument-specification/</link><pubDate>Thu, 20 May 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-role-argument-specification/</guid><description>&lt;p&gt;It has been a while since our last hardcore technical post. So we decided to
put steamy 
&lt;a target="_self" href="https://steampunk.si/blog/cloud-automation-with-ansible-series-dynamic-inventory/" title="Blog post about dynamic inventory" &gt;cloud posts&lt;/a&gt;
 aside for a moment and get down and dirty with one
of the new features of Ansible Core 2.11: argument specification for Ansible
roles.&lt;/p&gt;</description></item><item><title>Automating ServiceNow with Red Hat Ansible Automation Platform</title><link>https://steampunk.si/blog/automating-servicenow-with-red-hat-ansible-automaion-platform/</link><pubDate>Thu, 13 May 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/automating-servicenow-with-red-hat-ansible-automaion-platform/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/certified-collection-servicenow" title="Original article" &gt;Ansible blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;IT service management (ITSM) is a collection of policies and processes
for the management and support of IT services. The main focus of ITSM is
increasing the value of the customers service chain. But without the
proper automation support, providing IT services can quickly become a
major time-sink.&lt;/p&gt;</description></item><item><title>Cloud automation with Ansible series: Dynamic inventory</title><link>https://steampunk.si/blog/cloud-automation-with-ansible-series-dynamic-inventory/</link><pubDate>Thu, 06 May 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/cloud-automation-with-ansible-series-dynamic-inventory/</guid><description>&lt;p&gt;If you have any decent amount of servers in the cloud, you want to use automation to create and manage them.
Even with few servers, having your infrastructure specified as code serves the much-needed dual purpose of documenting
exactly what is necessary for your setup and giving you the ability to deploy and redeploy your stack quickly and
reliably.&lt;/p&gt;</description></item><item><title>Ansible: Add value to your product with IT automation</title><link>https://steampunk.si/blog/ansible-add-value-your-product-it-automation/</link><pubDate>Thu, 15 Apr 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-add-value-your-product-it-automation/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on 
&lt;a target="_blank" rel="noopener noreferrer" href="https://connect.redhat.com/blog/ansible-add-value-your-product-it-automation" title="Original article" &gt;Red Hat Partner Connect blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Think of IT automation with Ansible as the perfect way to
help customers by automating repeated tasks, product updates, management, and
provisioning of your product. Because of Ansible’s widespread adoption, chances
are your customers already realize the benefits of its integration with your
product and are looking forward to extending the use cases of Ansible inside
their organization.&lt;/p&gt;</description></item><item><title>5 tips for choosing an Ansible collection that's right for you</title><link>https://steampunk.si/blog/five-tips-for-choosing-an-ansible-collection/</link><pubDate>Wed, 31 Mar 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/five-tips-for-choosing-an-ansible-collection/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on 
&lt;a target="_blank" rel="noopener noreferrer" href="https://opensource.com/article/21/3/ansible-collections" title="Original article" &gt;Opensource.com&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;In August 2020, Ansible issued its first release since the developers split the
core functionality from the vast majority of its modules and plugins. A few

&lt;a target="_blank" rel="noopener noreferrer" href="https://docs.ansible.com/ansible/latest/collections/ansible/builtin/" title="List of built-in Ansible modules and plugins" &gt;basic Ansible modules&lt;/a&gt;
 remain part of core Ansible - modules
for templating configuration files, managing services, and installing packages.
All the other modules and plugins found their homes in dedicated 
&lt;a target="_blank" rel="noopener noreferrer" href="https://docs.ansible.com/ansible/latest/collections/index.html" title="List of Ansible collections" &gt;Ansible
collections&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Why Cloud Automation with Ansible is The Future</title><link>https://steampunk.si/blog/why-cloud-automation-with-ansible-is-the-future/</link><pubDate>Thu, 18 Feb 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/why-cloud-automation-with-ansible-is-the-future/</guid><description>&lt;p&gt;Cloud provisioning is a critical element of the modern cloud computing model.
We live in the age of microservices, where 
&lt;a target="_self" href="https://steampunk.si/blog/the-benefits-of-it-automation-and-why-you-should-start-using-it-now/" title="Post about automation benefits" &gt;automation&lt;/a&gt;
 is not a
nice-to-have anymore. It became an integral part of everyday operations.&lt;/p&gt;</description></item><item><title>Ansible Integration: Possible use cases for your product</title><link>https://steampunk.si/blog/ansible-integration-possible-use-cases-for-your-product/</link><pubDate>Wed, 27 Jan 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-integration-possible-use-cases-for-your-product/</guid><description>&lt;p&gt;Are you looking into creating an Ansible integration for your product? The
integration will 
&lt;a target="_self" href="https://steampunk.si/blog/short-guide-to-increasing-product-adoption-with-automation/" title="Post about increasing product adoption via automation" &gt;speed up the adoption of your product&lt;/a&gt;
, attract
new users, and ease its use. However, decide on an integration that doesn&amp;rsquo;t
fit your product and it will have no real value for your business.&lt;/p&gt;</description></item><item><title>Should you build or outsource the development of Ansible Collections?</title><link>https://steampunk.si/blog/should-you-build-or-outsource-the-development-of-ansible-collections/</link><pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/should-you-build-or-outsource-the-development-of-ansible-collections/</guid><description>&lt;p&gt;You are ready for an Ansible integration.&lt;/p&gt;
&lt;p&gt;Based on your initial research, developing Ansible integration for your
product will 
&lt;a target="_self" href="https://steampunk.si/blog/short-guide-to-increasing-product-adoption-with-automation/" title="Post about speeding up product adoption with automation" &gt;speed up adoption rate&lt;/a&gt;
 and attract new users.
However, there’s one important decision left to make - are you going to
develop the integration in-house, or will you outsource it to Ansible experts?&lt;/p&gt;</description></item><item><title>The benefits of IT automation and why you should start using it now</title><link>https://steampunk.si/blog/the-benefits-of-it-automation-and-why-you-should-start-using-it-now/</link><pubDate>Wed, 06 Jan 2021 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/the-benefits-of-it-automation-and-why-you-should-start-using-it-now/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.xlab.si/blog/the-benefits-of-it-automation-and-why-you-should-start-using-it-now/" title="Origina post" &gt;XLAB blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;IT automation is not a choice anymore, it&amp;rsquo;s a necessity. To stay competitive,
a business must optimize processes and enable employees to stop focusing on
routine tasks and start focusing on activities that create a competitive edge
on the market. But how to begin the automation of your IT processes? 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/" title="XLAB Steampunk home page" &gt;XLAB
Steampunk&lt;/a&gt;
 experts recommend Red Hat Ansible and help you with the
implementation of automation.&lt;/p&gt;</description></item><item><title>A Short Guide to Increasing Your Product Adoption with IT automation</title><link>https://steampunk.si/blog/short-guide-to-increasing-product-adoption-with-automation/</link><pubDate>Tue, 15 Dec 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/short-guide-to-increasing-product-adoption-with-automation/</guid><description>&lt;p&gt;Successful product adoption results in high user engagement and loyal brand
advocates who love your product and use it regularly. It&amp;rsquo;s the culmination of
customer satisfaction, and is a vital tenet that encourages others to purchase
your products.&lt;/p&gt;</description></item><item><title>The Importance Of Software Integrations For Your Product</title><link>https://steampunk.si/blog/importance-of-software-integrations-for-your-product/</link><pubDate>Tue, 01 Dec 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/importance-of-software-integrations-for-your-product/</guid><description>&lt;p&gt;Integration is a crucial aspect of any modern business. As businesses in every
industry are managing increasingly more complex systems, a shift towards
unified automation and DevOps principles is essential to stay competitive.&lt;/p&gt;</description></item><item><title>Why and how of the NGINX Unit Ansible Collection</title><link>https://steampunk.si/blog/why-and-how-of-the-nginx-unit-ansible-collection/</link><pubDate>Thu, 26 Nov 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/why-and-how-of-the-nginx-unit-ansible-collection/</guid><description>&lt;p&gt;At the beginning of July 2020, we started using the NGINX Unit application
server in one of our projects. Because we are not barbarians, we wanted to use
Ansible to automate the deployment. And this is where the &amp;ldquo;fun&amp;rdquo; started.&lt;/p&gt;
&lt;p&gt;In this post, we will give a short backstory about our NGINX Unit adoption,
continue with the reasons behind our decision to create a complete 
&lt;a target="_blank" rel="noopener noreferrer" href="https://docs.steampunk.si/unit/" title="NGINX Unit Ansible Collectoon documentation" &gt;Ansible
Collection&lt;/a&gt;
 instead of a simple Ansible role, and conclude with a
short development process overview.&lt;/p&gt;</description></item><item><title>Speed up Automation with Ansible Collections</title><link>https://steampunk.si/webinars-training/speed-up-automation-ansible-collections/</link><pubDate>Fri, 20 Nov 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/webinars-training/speed-up-automation-ansible-collections/</guid><description>&lt;p&gt;Automation is becoming the preferred method for adopting new technologies among users. High-quality
Ansible Collections help eliminate barriers to adoption and improve the reliability of onboarding new technology.
In this webinar, get ready to learn how to get from the “my collection exists” level to the “my collection really
speeds up the adoption of automation” level. Find out the value a high-quality Ansible Collection brings to
Ansible users and how it leads to successful automation of your products.&lt;/p&gt;</description></item><item><title>Managing Sensu Go 6 using Ansible</title><link>https://steampunk.si/blog/managing-sensu-go-6-using-ansible/</link><pubDate>Thu, 19 Nov 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/managing-sensu-go-6-using-ansible/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://blog.sensu.io/managing-sensu-go-6-using-ansible" title="Original blog post" &gt;Sensu Go blog&lt;/a&gt;
.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Earlier this year, we shared the certified 
&lt;a target="_blank" rel="noopener noreferrer" href="https://blog.sensu.io/automating-monitoring-with-the-sensu-go-ansible-collection" title="Sensu Go Ansible Collection announcement" &gt;Ansible Collection for Sensu
Go&lt;/a&gt;
, which makes it easy to automate your monitoring and achieve
real-time visibility into auto-scaling infrastructure. Now that 
&lt;a target="_blank" rel="noopener noreferrer" href="https://blog.sensu.io/unlocking-another-level-of-automation-with-sensu-go-6" title="Sensu Go 6 release announcement" &gt;Sensu Go 6
has been released&lt;/a&gt;
, we will share the latest updates on the Collection,
including the management aspects of Sensu Go 6, with a focus on the structure
of Ansible playbooks in the Sensu Go 6 world.&lt;/p&gt;</description></item><item><title>Intro to Testing Ansible Collections</title><link>https://steampunk.si/webinars-training/intro-testing-ansible-collections/</link><pubDate>Tue, 13 Oct 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/webinars-training/intro-testing-ansible-collections/</guid><description>&lt;p&gt;There’s no such thing as perfect code. However, for Ansible integrations to run smoothly, it’s crucial that Ansible
Collections are tested systematically to prevent bugs from entering the codebase. With a sturdy test suite in place,
you’ll be confident that the tested code produces the desired results and that any future modifications will not break
the backward compatibility.&lt;/p&gt;
&lt;p&gt;By the end of this FREE workshop, you’ll understand the value and benefits of testing, its setup, and different
types of tests accompanied with real-life examples.&lt;/p&gt;</description></item><item><title>Client Spotlight: Ansible integration helps Sensu reach more users</title><link>https://steampunk.si/blog/ansible-integration-helps-sensu-reach-more-users/</link><pubDate>Mon, 12 Oct 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-integration-helps-sensu-reach-more-users/</guid><description>&lt;p&gt;In order to provide a great experience to its users, &lt;strong&gt;Sensu&lt;/strong&gt; decided to
integrate its product with Ansible. The team outsourced the integration to
XLAB Steampunk for the best possible result. How did our collaboration work
out for them? Did Sensu&amp;rsquo;s Ansible Collection help them reach their goal?&lt;/p&gt;</description></item><item><title>Attract new users with high-quality Ansible Collections</title><link>https://steampunk.si/blog/attract-new-users-with-high-quality-ansible-collections/</link><pubDate>Tue, 06 Oct 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/attract-new-users-with-high-quality-ansible-collections/</guid><description>&lt;p&gt;The IT industry has been increasing in complexity for quite some time now.
Organizations have to find a way to manage an additional maintenance burden.
Most of them are trying to solve the problem via automation. But this cultural
shift towards the DevOps and site reliability engineering disciplines has one
significant consequence for &lt;strong&gt;product owners: automation is becoming the
preferred method for adopting new technologies&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Ansible module documentation reliability and compliance</title><link>https://steampunk.si/blog/ansible-module-documentation-and-compliance/</link><pubDate>Thu, 03 Sep 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-module-documentation-and-compliance/</guid><description>&lt;p&gt;Module documentation is an entry point for Ansible playbook authors. So it is
vitally important that we keep the said documentation in sync with the module
implementation or risk getting angry bug reports. But here lies the problem.&lt;/p&gt;</description></item><item><title>A day in a life of a Steampunk member</title><link>https://steampunk.si/blog/a-day-in-a-life-of-a-steampunk-member/</link><pubDate>Wed, 29 Jul 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/a-day-in-a-life-of-a-steampunk-member/</guid><description>&lt;p&gt;We write about different 
&lt;a target="_self" href="https://steampunk.si/blog/adding-integration-tests-to-ansible-content-collections/" title="Post about adding integration tests to Ansible collections" &gt;projects&lt;/a&gt;
 and 
&lt;a target="_self" href="https://steampunk.si/spotter/blog/aws-credentials-safety/" title="Post about using secrets in Ansible playbooks" &gt;topics&lt;/a&gt;
 on this
blog. But have you ever wondered what it is like to work, support, and write
about all those projects while also being a father of two children? Well, it is
&amp;ldquo;fun&amp;rdquo; ;)&lt;/p&gt;</description></item><item><title>Adding integration tests to Ansible Content Collections</title><link>https://steampunk.si/blog/adding-integration-tests-to-ansible-content-collections/</link><pubDate>Tue, 30 Jun 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/adding-integration-tests-to-ansible-content-collections/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/adding-integration-tests-to-ansible-content-collections" title="Original blog post" &gt;Ansible blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;In the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/migrating-existing-content-into-a-dedicated-ansible-collection" title="Previous installment of this post" &gt;previous installment&lt;/a&gt;
 of our &lt;em&gt;&amp;ldquo;let us create the best
Ansible Content Collection ever&amp;rdquo;&lt;/em&gt; saga, we covered the DigitalOcean-related
content migration process. What we ended up with was a 
&lt;a target="_blank" rel="noopener noreferrer" href="https://github.com/xlab-si/digital_ocean.digital_ocean/tree/1st-installment" title="Demonstration DigitalOcean collection" &gt;fully functioning
Ansible Content Collection&lt;/a&gt;
 that unfortunately had no tests.
But not for long; we will be adding an integration test for the droplet
module.&lt;/p&gt;</description></item><item><title>Enforcing Compliance using the AWS Ansible Collection</title><link>https://steampunk.si/blog/enforcing-compliance-using-aws-ansible-collection/</link><pubDate>Tue, 16 Jun 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/enforcing-compliance-using-aws-ansible-collection/</guid><description>&lt;p&gt;If you are responsible for managing a bunch of your organization&amp;rsquo;s AWS
resources, you probably know how annoying it is to debug various
deployment-related issues, only to learn that someone accidentally messed with
your setup, yet again. Which you probably resolved by navigating your
command-line history like a maniac (because you don&amp;rsquo;t use Ansible and have to
&lt;code&gt;Ctrl+R&lt;/code&gt;, as you also forgot to put down the setup instructions ;)). We&amp;rsquo;ve
been there, too. And this is what we learned:&lt;/p&gt;</description></item><item><title>AWS Ansible Collection: Dynamic EC2 Inventory</title><link>https://steampunk.si/blog/aws-inventory-plugin/</link><pubDate>Tue, 02 Jun 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/aws-inventory-plugin/</guid><description>&lt;p&gt;The Ansible inventory. Essential, yet often neglected part of Ansible. But not
today. Today, we will bring it into the spotlight it deserves, and demonstrate
some of its features that can help us simplify our life substantially when
dealing with Amazon EC2. And we will start with a little bit of set theory,
just like every other Ansible inventory blog post does ;)&lt;/p&gt;</description></item><item><title>AWS Ansible Collection: Getting started with IPv4 for Amazon VPC</title><link>https://steampunk.si/blog/aws-ansible-collection-vpc-getting-started/</link><pubDate>Tue, 19 May 2020 05:02:00 +0200</pubDate><guid>https://steampunk.si/blog/aws-ansible-collection-vpc-getting-started/</guid><description>&lt;p&gt;We&amp;rsquo;ve done a 
&lt;a target="_self" href="https://steampunk.si/blog/aws-ansible-collection-basic-usage/" title="Post about basic AWS Ansible Collection usage" &gt;Getting started with the AWS Ansible Collection&lt;/a&gt;

already, so this time we will go all in with the collection, aiming to set up a
fresh EC2 VPC complete with an instance that hosts a web server. To get there,
we will follow the steps in 
&lt;a target="_blank" rel="noopener noreferrer" href="http://web.archive.org/web/20191021192821/https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html" title="Getting Started with IPv4 for Amazon VPC" &gt;this article from Amazon&lt;/a&gt;
. And we
will do it all in Ansible. Educational, interesting and useful!&lt;/p&gt;</description></item><item><title>Migrating Existing Content Into a Dedicated Ansible Collection</title><link>https://steampunk.si/blog/migrating-existing-content-into-a-dedicated-ansible-collection/</link><pubDate>Tue, 12 May 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/migrating-existing-content-into-a-dedicated-ansible-collection/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/migrating-existing-content-into-a-dedicated-ansible-collection" title="Original blog post" &gt;Ansible blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Today, we will demonstrate how to migrate part of the existing Ansible content
(modules and plugins) into a dedicated Ansible Collection. We will be using
modules for managing DigitalOcean&amp;rsquo;s resources as an example so you can follow
along and test your development setup. But first, let us get the big question
out of the way: Why would we want to do that?&lt;/p&gt;</description></item><item><title>Getting Started with the AWS Ansible Collection</title><link>https://steampunk.si/blog/aws-ansible-collection-basic-usage/</link><pubDate>Wed, 06 May 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/aws-ansible-collection-basic-usage/</guid><description>&lt;p&gt;Configuring your infrastructure using our AWS Ansible Collection is simple.
Join us in pressing Enter to create your own infrastructure!&lt;/p&gt;</description></item><item><title>Say Hello to Enterprise AWS Ansible Collection</title><link>https://steampunk.si/blog/aws-ansible-collection-intro/</link><pubDate>Tue, 21 Apr 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/aws-ansible-collection-intro/</guid><description>&lt;p&gt;In the era of fast changes, it is next to impossible to keep the
infrastructure running manually. Why? Because there are just too many
different pieces that we must keep running in harmony. And no, waiting for
evolution to give us an additional finger or two for hyper-speed keyboard
bashing is not an option ;) Luckily, there is a better way of solving this
problem: &lt;strong&gt;automation&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Make integration tests for your Ansible Collection fast</title><link>https://steampunk.si/blog/make-collection-integration-tests-fast/</link><pubDate>Tue, 24 Mar 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/make-collection-integration-tests-fast/</guid><description>&lt;p&gt;Tests are great. Especially integration tests. But we need quite a lot of them
to cover the codebase. And because we want to run them as often as practically
possible, we must make sure our test suite is fast. What follows is a story of
how Steampunks made Sensu Go Ansible Collection&amp;rsquo;s test times as short as
possible.&lt;/p&gt;</description></item><item><title>Ansible Content Collections: The Sensu Go Use Case</title><link>https://steampunk.si/blog/sensu-go-ansible-collection-use-case/</link><pubDate>Mon, 10 Feb 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/sensu-go-ansible-collection-use-case/</guid><description>&lt;p&gt;&lt;em&gt;This post was originally published on the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/ansible-content-collections-the-sensu-go-use-case" title="Original blog post" &gt;Ansible blog&lt;/a&gt;
&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;In 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/getting-started-with-ansible-collections" title="Post about getting started with Ansible collections" &gt;Getting Started With Ansible Content Collections&lt;/a&gt;
, which
presented the general idea behind what is becoming a new standard in the
distribution of Ansible content, we learned about &lt;em&gt;the what&lt;/em&gt;, &lt;em&gt;the why&lt;/em&gt; and
&lt;em&gt;the how&lt;/em&gt; of Ansible Collections (and hopefully it got you excited about
Ansible Collections!). In this post, we&amp;rsquo;ll take things a bit further,
continuing the journey into the world of Ansible Collections accompanied by
the certified 
&lt;a target="_blank" rel="noopener noreferrer" href="https://galaxy.ansible.com/sensu/sensu_go" title="Sensu Go Ansible collection" &gt;Sensu Go Ansible Collection&lt;/a&gt;
 that our team at

&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/" title="XLAB Steampunk home page" &gt;XLAB Steampunk&lt;/a&gt;
 developed and supports for 
&lt;a target="_blank" rel="noopener noreferrer" href="https://sensu.io/" title="Sensu home page" &gt;Sensu&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>High-quality Ansible Collections e-book</title><link>https://steampunk.si/ebooks/importance-of-high-quality-ansible-collections/</link><pubDate>Sun, 02 Feb 2020 00:00:00 +0000</pubDate><guid>https://steampunk.si/ebooks/importance-of-high-quality-ansible-collections/</guid><description>&lt;h3 id="heres-what-youll-learn"&gt;Here’s what you’ll learn:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Why Ansible Collections add value to your existing solution&lt;/li&gt;
&lt;li&gt;Why it’s important to invest into a high-quality Collection and not develop it as a side project&lt;/li&gt;
&lt;li&gt;What “high-quality” actually means and how to ensure it&lt;/li&gt;
&lt;li&gt;How Sensu managed to attract new customers with their Ansible integration&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>How to benefit from Ansible Collections</title><link>https://steampunk.si/blog/ansible-collection-benefits/</link><pubDate>Thu, 05 Dec 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/ansible-collection-benefits/</guid><description>&lt;p&gt;Today, we can’t imagine managing complex IT environments without efficient
automation, and luckily, we don’t have to owing to ingenious tools such as
Ansible.&lt;/p&gt;</description></item><item><title>Documenting Ansible Collections</title><link>https://steampunk.si/blog/documenting-ansible-collections/</link><pubDate>Tue, 22 Oct 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/documenting-ansible-collections/</guid><description>&lt;p&gt;It is a well-known fact that real programmers do not document their code. If
it was hard to write, it should be hard to understand and use. But this
attitude might prove itself to be a bit problematic if we would like to get
paid for our work. And because we do not want to see you all broke, we will
show you how to document your Ansible collections using 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.sphinx-doc.org/" title="Sphinx&amp;#39;s home page" &gt;Sphinx&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>The Galactic Future of Ansible Content</title><link>https://steampunk.si/blog/the-galactic-future-of-ansible-content/</link><pubDate>Mon, 16 Sep 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/the-galactic-future-of-ansible-content/</guid><description>&lt;p&gt;Ansible project is 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/thoughts-on-restructuring-the-ansible-project" title="Thoughts on Restructuring the Ansible Project" &gt;maturing&lt;/a&gt;
 and changing the way we 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/blog/the-future-of-ansible-content-delivery" title="The future of Ansible content delivery" &gt;deliver&lt;/a&gt;
 Ansible
content to the users. And while Ansible Galaxy is already a goto place for
finding roles, it is now becoming a central hub for all things Ansible. So you
might wonder: how does this change affect us: the community of Ansible content
producers?&lt;/p&gt;</description></item><item><title>Let us give Ansible a REST</title><link>https://steampunk.si/blog/let-us-give-ansible-a-rest/</link><pubDate>Wed, 19 Jun 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/let-us-give-ansible-a-rest/</guid><description>&lt;p&gt;It is becoming increasingly difficult to find a home or office product that
cannot be controlled using some kind of 
&lt;a target="_blank" rel="noopener noreferrer" href="https://en.wikipedia.org/wiki/Web_API" title="Wikipedia article on web APIs" &gt;web application programming interface
(API)&lt;/a&gt;
. Smart light bulbs, robotic lawn mowers, espresso machines - they
all have it. Wouldn&amp;rsquo;t it be cool if we could use Ansible to control them?&lt;/p&gt;</description></item><item><title>Taking Ansible apart</title><link>https://steampunk.si/blog/taking-ansible-apart/</link><pubDate>Wed, 03 Apr 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/taking-ansible-apart/</guid><description>&lt;p&gt;&lt;em&gt;This post was reviewed in August 2024 and remains up-to-date with the latest Ansible changes.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Unless you have been living under a rock, you have probably already heard about

&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com/" title="Red Hat Ansible home page" &gt;Ansible&lt;/a&gt;
 and how it can make your job of maintaining company infrastructure
easier. But have you ever asked yourself what exactly Ansible is and how it
works? We have and this is what we discovered.&lt;/p&gt;</description></item><item><title>Provisioning bare metal servers using ManageIQ</title><link>https://steampunk.si/blog/miq-bare-metal-provisioning/</link><pubDate>Tue, 26 Mar 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/miq-bare-metal-provisioning/</guid><description>&lt;p&gt;It seems that today almost anyone knows how to provision a virtual machine in
the cloud: simply select an operating system image of choice along with an
instance type and you are one click away from a working virtual machine. But
what about bare metal servers? Is it possible to provision them with the same
ease? Let us find out.&lt;/p&gt;</description></item><item><title>Managing pixies with style</title><link>https://steampunk.si/blog/managing-pixies-with-style/</link><pubDate>Thu, 14 Feb 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/managing-pixies-with-style/</guid><description>&lt;p&gt;Managing preboot execution environment (PXE) boot configurations for different
computers is really tedious and error-prone when done manually. There exist
various projects like 
&lt;a target="_blank" rel="noopener noreferrer" href="https://cobbler.github.io/" title="Cobbler home page" &gt;Cobbler&lt;/a&gt;
 that try to address this problem, but in
this post, we will be using 
&lt;a target="_blank" rel="noopener noreferrer" href="https://manageiq.org/" title="ManageIQ home page" &gt;ManageIQ&lt;/a&gt;
 to manage the PXE server and its
content.&lt;/p&gt;</description></item><item><title>How to train your pixies</title><link>https://steampunk.si/blog/how-to-train-your-pixies/</link><pubDate>Wed, 30 Jan 2019 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/how-to-train-your-pixies/</guid><description>&lt;p&gt;Setting up a preboot execution environment (PXE) server is relatively
straightforward task once you know how various pieces fit together. But
setting it up for the first time can be quite a challenge. And if you think
&amp;ldquo;Hey, there are already countless semi-working tutorials on the internet&amp;rdquo;,
well, we have got some good news for you: ours is fully-working ;)&lt;/p&gt;</description></item><item><title>Ansible Playbook as an Event Callback in CloudForms</title><link>https://steampunk.si/blog/nuage-ansible-in-automate/</link><pubDate>Tue, 18 Sep 2018 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/nuage-ansible-in-automate/</guid><description>&lt;p&gt;Running your own 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com"&gt;Ansible&lt;/a&gt;
 playbooks upon 
&lt;a target="_blank" rel="noopener noreferrer" href="http://manageiq.org"&gt;ManageIQ&lt;/a&gt;
/
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.redhat.com/en/technologies/management/cloudforms"&gt;CloudForms&lt;/a&gt;
 provider event opens
unimaginable possibilities to automate your data centers. This blogpost and accompanying

&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=YeXtnjTY67s"&gt;YouTube video&lt;/a&gt;
 is a step-by-step tutorial that will
show you how to unleash the power of Ansible within CloudForms. Our example is based on

&lt;a target="_blank" rel="noopener noreferrer" href="http://nuagenetworks.net"&gt;Nuage Networks&lt;/a&gt;
 provider and focuses on triggering a playbook executed
when a &amp;ldquo;new enterprise was created&amp;rdquo; event occurs on remote server. The playbook connects to the
remote server and automatically provisions a dozen of entites in the newly created enterprise.&lt;/p&gt;</description></item><item><title>Dynamic UI for ManageIQ Provider Operations</title><link>https://steampunk.si/blog/nuage-react-component/</link><pubDate>Thu, 16 Aug 2018 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/nuage-react-component/</guid><description>&lt;p&gt;Having read our blogpost about

&lt;a target="_blank" rel="noopener noreferrer" href="https://tech.xlab.si/blog/nuage-ansible-operations"&gt;Implementing ManageIQ Provider Operations with Ansible&lt;/a&gt;

one might be wondering about how to capture Ansible playbook inputs from user.
Isn&amp;rsquo;t it difficult to provide a custom native UI form in ManageIQ that would
capture user inputs like subnet name, address and netmask?&lt;/p&gt;
&lt;p&gt;Well, it &lt;em&gt;used to&lt;/em&gt; be a big pain to implement any dynamic and fully-customized HTML form for
a ManageIQ provider. But not anymore. Just a few days ago the

&lt;a target="_blank" rel="noopener noreferrer" href="https://github.com/ManageIQ/manageiq-ui-classic/pull/4262"&gt;ManageIQ UI team introduced&lt;/a&gt;

support for 
&lt;a target="_blank" rel="noopener noreferrer" href="https://reactjs.org"&gt;React&lt;/a&gt;
 Components that &lt;strong&gt;live in a provider codebase&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;We immediately fell in love. So much that we simply had to share the story with you,
fellow developers.&lt;/p&gt;</description></item><item><title>Implementing ManageIQ Provider Operations with Ansible</title><link>https://steampunk.si/blog/nuage-ansible-operations/</link><pubDate>Thu, 09 Aug 2018 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/nuage-ansible-operations/</guid><description>&lt;p&gt;Traditional way of integrating 
&lt;a target="_blank" rel="noopener noreferrer" href="http://manageiq.org"&gt;ManageIQ&lt;/a&gt;
 provider operations is to bake them
in code of the provider core, adhering to certain specifics of the provider API.
While this is perfectly valid and has served the purposes well for years,
ManageIQ team investigated options for superior flexibility.&lt;/p&gt;
&lt;p&gt;This post explains how we did it using 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.ansible.com"&gt;Ansible&lt;/a&gt;
 on a real example for
the 
&lt;a target="_blank" rel="noopener noreferrer" href="http://www.nuagenetworks.net"&gt;Nuage Networks&lt;/a&gt;
 provider. It will serve other adventurous developers
getting started with Ansible within ManageIQ.&lt;/p&gt;</description></item><item><title>ManageIQ and Redfish, sitting in a tree ...</title><link>https://steampunk.si/blog/manageiq-redfish/</link><pubDate>Thu, 26 Jul 2018 00:00:00 +0000</pubDate><guid>https://steampunk.si/blog/manageiq-redfish/</guid><description>&lt;p&gt;&amp;hellip; K-I-S-S-I-N-G. First comes read-only inventory support, then comes ability
to perform simple actions, then comes support for system provisioning, um, in
a baby carriage ;) And for those of you who do not speak childish, we will be
talking about 
&lt;a target="_blank" rel="noopener noreferrer" href="http://manageiq.org/" title="ManageIQ home page" &gt;ManageIQ&lt;/a&gt;
 and 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.dmtf.org/standards/redfish" title="Redfish standard API" &gt;Redfish&lt;/a&gt;
 integration.&lt;/p&gt;</description></item><item><title>Fishing Around in the Sea of Hardware</title><link>https://steampunk.si/blog/redfish-intro/</link><pubDate>Thu, 31 May 2018 07:31:58 +0200</pubDate><guid>https://steampunk.si/blog/redfish-intro/</guid><description>&lt;p&gt;Have you ever thought about how Amazon and the likes manage to take care of
all their servers? And no, buying admins 
&lt;a target="_blank" rel="noopener noreferrer" href="https://segway.com" title="Segway home page" &gt;Segways&lt;/a&gt;
 to drive around the
data center is not the right answer (albeit a cool one). Interested?&lt;/p&gt;</description></item><item><title/><link>https://steampunk.si/ansible-collections/aws/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/ansible-collections/aws/</guid><description/></item><item><title/><link>https://steampunk.si/ansible-collections/nginx-unit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/ansible-collections/nginx-unit/</guid><description/></item><item><title/><link>https://steampunk.si/ansible-collections/sensu/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/ansible-collections/sensu/</guid><description/></item><item><title/><link>https://steampunk.si/ansible-collections/servicenow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/ansible-collections/servicenow/</guid><description/></item><item><title/><link>https://steampunk.si/ansible-upgrades/accelerate-migration-aap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/ansible-upgrades/accelerate-migration-aap/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/assistant/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/assistant/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/automation-survey/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/automation-survey/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/faq/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/getting-started/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/onprem-testing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/onprem-testing/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/analytics-and-reporting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/analytics-and-reporting/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/automation-security-and-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/automation-security-and-governance/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/compliance-validation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/compliance-validation/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/custom-policies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/custom-policies/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/enterprise-ready/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/enterprise-ready/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/integrations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/integrations/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/mcp/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/mcp/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/playbook-scanning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/playbook-scanning/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/platform/team-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/platform/team-management/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/pricing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/pricing/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/simple-time-savings-calculator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/simple-time-savings-calculator/</guid><description/></item><item><title/><link>https://steampunk.si/spotter/time-savings-calculator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/time-savings-calculator/</guid><description/></item><item><title> Manage Teams and Collaborate</title><link>https://steampunk.si/spotter/getting-started/manage-teams-and-collaborate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/manage-teams-and-collaborate/</guid><description>&lt;p&gt;With Spotter, it’s a breeze to collaborate with others, cultivate a shared workspace and bring diverse types of users and teams in the automation chain closer together. If you understand how and when the automation is run, you can focus more on delivering the results you want to achieve. See 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=hLcFQQk8Ce4"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/keep-track-of-scan-history-and-collaborate-with-your-team/"&gt;blog&lt;/a&gt;
.&lt;/p&gt;
&lt;h2 id="invite-new-members"&gt;Invite New Members &lt;/h2&gt;
&lt;p&gt;To add users to your organization, simply send an invitation. Go to members tab, click on Invite new member, and provide user’s email.&lt;/p&gt;</description></item><item><title>15-Minute quick call</title><link>https://steampunk.si/spotter/book-a-demo/15-minute-quick-call/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/book-a-demo/15-minute-quick-call/</guid><description>&lt;div class="tidycal-embed" data-path="steampunk/15-minute-quick-call"&gt;&lt;/div&gt;</description></item><item><title>30-Minute short demo</title><link>https://steampunk.si/spotter/book-a-demo/30-minute-short-demo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/book-a-demo/30-minute-short-demo/</guid><description>&lt;div class="tidycal-embed" data-path="steampunk/30-minute-short-demo"&gt;&lt;/div&gt;</description></item><item><title>60-Minute deep dive</title><link>https://steampunk.si/spotter/book-a-demo/60-minute-deep-dive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/book-a-demo/60-minute-deep-dive/</guid><description>&lt;div class="tidycal-embed" data-path="steampunk/60-minute-deep-dive"&gt;&lt;/div&gt;</description></item><item><title>AAP 2.7 is here - Are your Ansible Playbooks ready for it? | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/aap-2-7-is-here-are-your-ansible-playbooks-ready-for-it/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/aap-2-7-is-here-are-your-ansible-playbooks-ready-for-it/</guid><description>&lt;p&gt;Deprecated modules, changed syntax, tasks that ran fine on the previous version and fail silently on the next. At enterprise scale, that means weeks of manual triage before you can move safely.&lt;/p&gt;
&lt;p&gt;In this 30-minute session, we’ll walk you through &lt;strong&gt;what’s new in AAP 2.7 and what it does to your existing Playbook estate.&lt;/strong&gt; You’ll see a live Steampunk Spotter scan and explore &lt;strong&gt;three real enterprise case studies&lt;/strong&gt; – teams who’ve done this at scale: a Fortune 100 bank (132,000 issues, 128,000 auto-fixed, 3 months), a major U.S. bank migrating from legacy AWX (57,000+ tasks auto-rewritten, 7,600+ hours saved), and a global financial messaging provider (~2,000 Playbooks, 3-month migration target).&lt;/p&gt;</description></item><item><title>Agentic AI governance</title><link>https://steampunk.si/spotter/glossary/agentic-ai-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/agentic-ai-governance/</guid><description>&lt;p&gt;&lt;strong&gt;Agentic AI governance&lt;/strong&gt; is the set of controls for AI agents that take actions on their own, such as writing and committing code, calling APIs or changing infrastructure. It defines what an agent may do, which approvals it needs, how its actions are verified and logged, and how to stop it when something goes wrong.&lt;/p&gt;
&lt;p&gt;Agents raise the stakes compared with chat assistants. An assistant suggests code that a person reviews. An agent can open a pull request, respond to review comments and, with the wrong permissions, push changes into a deployment pipeline.&lt;/p&gt;</description></item><item><title>AI code governance</title><link>https://steampunk.si/spotter/glossary/ai-code-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ai-code-governance/</guid><description>&lt;p&gt;&lt;strong&gt;AI code governance&lt;/strong&gt; is the set of policies and automated checks an organization uses to make sure code written by AI coding assistants meets the same security, compliance and quality standards as code written by people. It controls what AI tools can generate, verifies their output before it ships, and records evidence for audits.&lt;/p&gt;
&lt;p&gt;AI coding assistants write code quickly, but they don&amp;rsquo;t know your internal policies, approved versions or regulatory obligations. For infrastructure code, that risk is concrete: a generated Ansible Playbook or Terraform plan changes real systems.&lt;/p&gt;</description></item><item><title>AI coding agent</title><link>https://steampunk.si/spotter/glossary/ai-coding-agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ai-coding-agent/</guid><description>&lt;p&gt;An &lt;strong&gt;AI coding agent&lt;/strong&gt; is an AI system that can complete software tasks with some autonomy: reading a codebase, planning changes, editing several files, running commands and tests, and iterating on the results. Unlike a code-completion assistant, an agent works toward a goal across many steps with limited human input.&lt;/p&gt;
&lt;p&gt;Examples include agent modes in GitHub Copilot and Cursor, Claude Code, and similar command-line and IDE agents. Teams use them for refactors, test writing, upgrades, and increasingly for infrastructure code such as Ansible Playbooks and Terraform modules.&lt;/p&gt;</description></item><item><title>All Spotter Commands</title><link>https://steampunk.si/spotter/getting-started/all-spotter-commands/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/all-spotter-commands/</guid><description>&lt;p&gt;Using Spotter is simple. You just need to know a few simple commands to make your Ansible Playbooks spotless. And don’t worry, you can look them up anytime by running s &lt;code&gt;--help&lt;/code&gt; in Spotter CLI. Dive in!
&lt;br&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;To scan&lt;/strong&gt;&lt;/p&gt;
&lt;div class="table table-1 d-none d-lg-block"&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan playbook.yml&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Perform a simple default scan.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/playbook&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan a playbook.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/taskfile1.yaml&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan a taskfile.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/role&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan a role.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/collection&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan an Ansible Collection.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/folder&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan any folder that contains Ansible content.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/playbook1.yaml path/to/playbook2.yaml&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan two playbooks.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/role1 path/to/role2&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan two roles.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/playbook1.yaml path/to/playbook2.yaml&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan multiple playbooks at once.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/taskfile.yaml path/to/playbook.yaml path/to/role path/to/collection&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan multiple files at once.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;div class="copy-code"&gt;&lt;div class="copy-code-inner"&gt;&lt;span class="pl-2"&gt;$&lt;/span&gt;&lt;code class="copied-text"&gt;spotter scan path/to/playbook/folder/play_*.yaml&lt;/code&gt;&lt;span class="copied"&gt;Copied!&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;
 &lt;td style="text-align: center"&gt;Scan multiple playbooks using glob.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;div class="d-block d-lg-none container table-sm"&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan playbook.yml&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Perform a simple default scan.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/playbook&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan a playbook.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/taskfile1.yaml	st&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;	Scan a taskfile.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/role&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan a role.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/collection&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan an Ansible Collection.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/folder&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan any folder that contains Ansible content.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/playbook1.yaml path/to/playbook2.yaml&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan two playbooks.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/role1 path/to/role2&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan two roles.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/playbook1.yaml path/to/playbook2.yaml&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan multiple playbooks at once.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/taskfile.yaml path/to/playbook.yaml path/to/role path/to/collection&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan multiple files at once.&lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="row row-wrap"&gt;
 &lt;div class="col-12 cell cell-top"&gt;
 &lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;spotter scan path/to/playbook/folder/play_*.yaml&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;/div&gt;
 &lt;div class="col-12 cell cell-bottom"&gt;Scan multiple playbooks using glob.&lt;/div&gt;
 &lt;/div&gt;
&lt;/div&gt;
&lt;br&gt;
&lt;p&gt;&lt;strong&gt;To set scanning profile&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Analytics and Reporting</title><link>https://steampunk.si/spotter/getting-started/analytics-and-reporting/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/analytics-and-reporting/</guid><description>&lt;p&gt;No matter where you perform your scans, you can see the scan history and analytics in the Spotter app, enabling you to track the frequency of failed playbook executions, identify common errors, spot trends, and monitor progress. You do not have to spend hours searching for the source of the problem. Addressing playbook pain points and finding potential solutions has never been faster, easier, and most importantly – more transparent. Watch 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=NNjxuDEYX74"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/keep-track-of-scan-history-and-collaborate-with-your-team/"&gt;blog&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Ansible</title><link>https://steampunk.si/spotter/glossary/ansible/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible/</guid><description>&lt;p&gt;&lt;strong&gt;Ansible&lt;/strong&gt; is an IT automation tool, maintained by Red Hat, that configures systems, deploys software and orchestrates multi-step workflows. It&amp;rsquo;s agentless: Ansible connects to managed machines over SSH or WinRM and runs tasks described in YAML files called Playbooks, so nothing needs to be installed on the targets.&lt;/p&gt;
&lt;p&gt;Ansible is used for configuration management, application deployment, patching, cloud provisioning, network automation and security compliance. It&amp;rsquo;s especially common for Day 2 operations across large Linux, Windows and network estates.&lt;/p&gt;</description></item><item><title>Ansible Automation Platform (AAP)</title><link>https://steampunk.si/spotter/glossary/ansible-automation-platform/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-automation-platform/</guid><description>&lt;p&gt;&lt;strong&gt;Red Hat Ansible Automation Platform (AAP)&lt;/strong&gt; is Red Hat&amp;rsquo;s enterprise product for running Ansible at scale. It adds a web UI and API, role-based access control, scheduling, credential management, certified content, execution environments and Event-Driven Ansible on top of open source Ansible, with Red Hat support.&lt;/p&gt;
&lt;p&gt;AAP is an execution platform: it runs Playbooks against infrastructure. Its automation controller is the successor of Ansible Tower, and private automation hub hosts approved Collections.&lt;/p&gt;</description></item><item><title>Ansible check mode (dry run)</title><link>https://steampunk.si/spotter/glossary/ansible-check-mode/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-check-mode/</guid><description>&lt;p&gt;&lt;strong&gt;Ansible check mode&lt;/strong&gt; is a dry run that predicts what a Playbook would change without making changes. Run it with &lt;code&gt;ansible-playbook site.yml --check&lt;/code&gt;, and add &lt;code&gt;--diff&lt;/code&gt; to see line-by-line differences in files and templates. Tasks report &amp;ldquo;changed&amp;rdquo; or &amp;ldquo;ok&amp;rdquo; as if they had run.&lt;/p&gt;
&lt;p&gt;Check mode has limits. It still connects to every managed host, so it needs inventory, credentials and network access. Modules that don&amp;rsquo;t support check mode are skipped, and tasks that depend on earlier changes can give misleading results.&lt;/p&gt;</description></item><item><title>Ansible Collection</title><link>https://steampunk.si/spotter/glossary/ansible-collection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-collection/</guid><description>&lt;p&gt;An &lt;strong&gt;Ansible Collection&lt;/strong&gt; is a distribution format that bundles modules, plugins, roles, Playbooks and documentation into one versioned package. Collections are named &lt;code&gt;namespace.collection&lt;/code&gt;, such as &lt;code&gt;amazon.aws&lt;/code&gt; or &lt;code&gt;community.general&lt;/code&gt;, and are installed from Ansible Galaxy or Red Hat Automation Hub.&lt;/p&gt;
&lt;p&gt;Collections let content be released independently of ansible-core. That speeds up fixes, but it also means a Playbook depends on several versions at once: ansible-core plus every Collection it uses.&lt;/p&gt;
&lt;p&gt;Certified Collections on Red Hat Automation Hub are tested and supported for AAP. XLAB Steampunk builds Red Hat Certified Ansible Collections, and Steampunk Spotter checks module and Collection compatibility in every Playbook.&lt;/p&gt;</description></item><item><title>Ansible Galaxy requirements.yml</title><link>https://steampunk.si/spotter/glossary/ansible-requirements-yml/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-requirements-yml/</guid><description>&lt;p&gt;&lt;strong&gt;requirements.yml&lt;/strong&gt; is a file that lists the Collections and roles an Ansible project depends on, with their sources and versions. Running &lt;code&gt;ansible-galaxy install -r requirements.yml&lt;/code&gt; installs everything listed, so every developer and CI/CD job uses the same dependencies.&lt;/p&gt;
&lt;h2 id="requirementsyml-example"&gt;requirements.yml example&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;collections:
 - name: amazon.aws
 version: &amp;#34;==8.0.0&amp;#34;
 - name: community.general
 version: &amp;#34;&amp;gt;=9.0.0,&amp;lt;10.0.0&amp;#34;
roles:
 - name: geerlingguy.nginx
 version: &amp;#34;3.2.0&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Pin versions. An unpinned Collection can introduce a breaking change into a Playbook that hasn&amp;rsquo;t been touched. The file is also the starting point for an Ansible SBOM.&lt;/p&gt;</description></item><item><title>Ansible inventory</title><link>https://steampunk.si/spotter/glossary/ansible-inventory/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-inventory/</guid><description>&lt;p&gt;An &lt;strong&gt;Ansible inventory&lt;/strong&gt; is the list of managed hosts that Ansible can automate, organized into groups. It can be a static file in INI or YAML format, or a dynamic inventory that pulls hosts from a cloud provider or CMDB. Playbooks target hosts and groups by name from the inventory.&lt;/p&gt;
&lt;h2 id="ansible-inventory-example-yaml"&gt;Ansible inventory example (YAML)&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;all:
 children:
 webservers:
 hosts:
 web1.example.com:
 web2.example.com:
 dbservers:
 hosts:
 db1.example.com:
 ansible_user: admin
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Host and group variables can live in the inventory or in &lt;code&gt;host_vars/&lt;/code&gt; and &lt;code&gt;group_vars/&lt;/code&gt; directories. The default inventory path is &lt;code&gt;/etc/ansible/hosts&lt;/code&gt;; pass another with &lt;code&gt;-i&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Ansible module</title><link>https://steampunk.si/spotter/glossary/ansible-module/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-module/</guid><description>&lt;p&gt;An &lt;strong&gt;Ansible module&lt;/strong&gt; is a reusable unit of code that performs one specific action on a managed host, such as copying a file, installing a package or creating a user. Tasks in a Playbook call modules with arguments, and well-written modules are idempotent: they only make a change when the system isn&amp;rsquo;t already in the requested state.&lt;/p&gt;
&lt;p&gt;Core modules ship in the &lt;code&gt;ansible.builtin&lt;/code&gt; Collection, such as &lt;code&gt;ansible.builtin.copy&lt;/code&gt;, &lt;code&gt;ansible.builtin.file&lt;/code&gt;, &lt;code&gt;ansible.builtin.user&lt;/code&gt; and &lt;code&gt;ansible.builtin.command&lt;/code&gt;. Thousands more come from Collections for cloud, network and security platforms.&lt;/p&gt;</description></item><item><title>Ansible Molecule</title><link>https://steampunk.si/spotter/glossary/ansible-molecule/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-molecule/</guid><description>&lt;p&gt;&lt;strong&gt;Molecule&lt;/strong&gt; is an open source testing framework for Ansible roles, Playbooks and Collections. It creates temporary test instances, usually containers or virtual machines, applies your code, runs it again to confirm idempotence, runs verification tests and then destroys the instances. &lt;code&gt;molecule test&lt;/code&gt; runs the full sequence.&lt;/p&gt;
&lt;p&gt;Molecule tests whether a role actually works. It needs real or containerized hosts and runs slower than static checks, so teams usually run it on role changes, not on every commit to every Playbook.&lt;/p&gt;</description></item><item><title>Ansible Playbook</title><link>https://steampunk.si/spotter/glossary/ansible-playbook/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-playbook/</guid><description>&lt;p&gt;An &lt;strong&gt;Ansible Playbook&lt;/strong&gt; is a YAML file that describes the desired state of systems as an ordered list of plays. Each play targets a group of hosts from the inventory and runs tasks, where every task calls an Ansible module. Playbooks are Ansible&amp;rsquo;s main unit of automation.&lt;/p&gt;
&lt;h2 id="sample-ansible-playbook"&gt;Sample Ansible Playbook&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;- name: Install and start nginx
 hosts: webservers
 become: true
 tasks:
 - name: Install nginx
 ansible.builtin.dnf:
 name: nginx
 state: present

 - name: Start and enable nginx
 ansible.builtin.service:
 name: nginx
 state: started
 enabled: true
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Run it with &lt;code&gt;ansible-playbook -i inventory.yml site.yml&lt;/code&gt;. Useful options include &lt;code&gt;--check&lt;/code&gt; (dry run), &lt;code&gt;--diff&lt;/code&gt;, &lt;code&gt;--limit&lt;/code&gt; and &lt;code&gt;-e&lt;/code&gt; for extra variables.&lt;/p&gt;</description></item><item><title>Ansible role</title><link>https://steampunk.si/spotter/glossary/ansible-role/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-role/</guid><description>&lt;p&gt;An &lt;strong&gt;Ansible role&lt;/strong&gt; is a standard way to package related tasks, variables, handlers, templates and files so they can be reused across Playbooks and projects. A role for &amp;ldquo;nginx,&amp;rdquo; for example, contains everything needed to install, configure and run nginx, and any Playbook can apply it with one line.&lt;/p&gt;
&lt;h2 id="ansible-role-structure"&gt;Ansible role structure&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;roles/nginx/
 tasks/main.yml
 handlers/main.yml
 defaults/main.yml
 vars/main.yml
 templates/
 files/
 meta/main.yml
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;code&gt;defaults/main.yml&lt;/code&gt; holds variables meant to be overridden; &lt;code&gt;meta/main.yml&lt;/code&gt; holds metadata and dependencies.&lt;/p&gt;</description></item><item><title>Ansible Tower and AWX</title><link>https://steampunk.si/spotter/glossary/ansible-tower-awx/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-tower-awx/</guid><description>&lt;p&gt;&lt;strong&gt;Ansible Tower&lt;/strong&gt; was Red Hat&amp;rsquo;s web-based UI and REST API for running Ansible with access control, scheduling and logging. With Ansible Automation Platform 2, Tower was renamed automation controller and became one component of AAP. It&amp;rsquo;s no longer sold as a separate product.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;AWX&lt;/strong&gt; is the free, open source upstream project behind Ansible Tower and automation controller. It provides a similar web UI and API, but it&amp;rsquo;s community-supported, releases frequently and isn&amp;rsquo;t recommended by Red Hat for production.&lt;/p&gt;</description></item><item><title>Ansible variable precedence</title><link>https://steampunk.si/spotter/glossary/ansible-variable-precedence/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-variable-precedence/</guid><description>&lt;p&gt;&lt;strong&gt;Ansible variable precedence&lt;/strong&gt; is the order Ansible uses to decide which value wins when the same variable is defined in several places. Ansible&amp;rsquo;s documentation lists 22 levels. Role defaults have the lowest precedence and extra vars passed with &lt;code&gt;-e&lt;/code&gt; on the command line always have the highest.&lt;/p&gt;
&lt;p&gt;A simplified order, from lowest to highest: role defaults, inventory group vars, inventory host vars, play vars, role vars, task vars, &lt;code&gt;set_fact&lt;/code&gt; and registered vars, extra vars.&lt;/p&gt;</description></item><item><title>ansible-core</title><link>https://steampunk.si/spotter/glossary/ansible-core/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-core/</guid><description>&lt;p&gt;&lt;strong&gt;ansible-core&lt;/strong&gt; is the minimal engine of Ansible: the language, runtime, command-line tools and the &lt;code&gt;ansible.builtin&lt;/code&gt; Collection. The &amp;ldquo;ansible&amp;rdquo; community package installs ansible-core plus a curated set of Collections. The two are versioned separately, so each community package release depends on a specific ansible-core version.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ansible --version&lt;/code&gt; shows the installed ansible-core version, the config file in use and the Python version. &lt;code&gt;ansible-galaxy collection list&lt;/code&gt; shows installed Collection versions.&lt;/p&gt;
&lt;p&gt;Each ansible-core release can drop support for Python versions, remove deprecated features and change module behavior. Upgrades are where Playbooks break most often. Steampunk Spotter checks Playbooks against a target ansible-core version before you upgrade, and an internal benchmark showed 8× faster migration to Red Hat AAP.&lt;/p&gt;</description></item><item><title>ansible.cfg</title><link>https://steampunk.si/spotter/glossary/ansible-cfg/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-cfg/</guid><description>&lt;p&gt;&lt;strong&gt;ansible.cfg&lt;/strong&gt; is Ansible&amp;rsquo;s configuration file. It sets defaults for how Ansible behaves, such as the inventory path, remote user, privilege escalation, SSH settings, roles and Collections paths, and number of parallel forks. Settings in it apply to every Ansible command run with that file.&lt;/p&gt;
&lt;p&gt;Ansible uses the first file it finds, in this order:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The path in the &lt;code&gt;ANSIBLE_CONFIG&lt;/code&gt; environment variable.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ansible.cfg&lt;/code&gt; in the current directory.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;~/.ansible.cfg&lt;/code&gt; in the home directory.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;/etc/ansible/ansible.cfg&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="ansiblecfg-example"&gt;ansible.cfg example&lt;/h2&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;[defaults]
inventory = ./inventory.yml
remote_user = automation
forks = 20
roles_path = ./roles
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Generate a fully commented file with &lt;code&gt;ansible-config init --disabled &amp;gt; ansible.cfg&lt;/code&gt;, and see active settings with &lt;code&gt;ansible-config dump --only-changed&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Assisted Playbook Writing</title><link>https://steampunk.si/spotter/getting-started/assisted-playbook-writing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/assisted-playbook-writing/</guid><description>&lt;p&gt;Spotter Assisted Writing feature speeds up your playbook writing even more. All you need to do is define your automation goals and Spotter will suggest suitable tasks and even whole playbooks when possible. Keep in mind, this feature is available only in Spotter VSC extension (jump to &lt;a class="thin-underlined-link" href="https://steampunk.si/spotter/getting-started/integrations/"&gt;Spotter Integrations &lt;/a&gt; to learn more about the VSC extension). Watch 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=Vc4NvCmFw68"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/ansible-playbooks-steampunk-spotter-assisted-writing/"&gt;blog&lt;/a&gt;
.&lt;/p&gt;
&lt;h4 aria-level="2" id="get-inline-suggestions"&gt;Get Inline Suggestions&lt;/h4&gt;
&lt;p&gt;By enabling the feature’s settings, you can access a wealth of time-saving suggestions that enhance playbook writing. Spotter allows you to set the number of suggestions displayed, giving you complete control over the assistance level. You simply type in:&lt;/p&gt;</description></item><item><title>Assure Secure Playbook Execution </title><link>https://steampunk.si/spotter/getting-started/assure-secure-playbook-execution/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/assure-secure-playbook-execution/</guid><description>&lt;p&gt;How to make sure your playbooks are secure, especially when dealing with hundreds or thousands of playbooks? When using Ansible Playbook platforms like Steampunk Spotter, offering full control over playbooks, assuring their security is a breeze.&lt;/p&gt;
&lt;h2 id="1-conduct-in-depth-playbook-analysis"&gt;1. Conduct in-depth playbook analysis&lt;/h2&gt;
&lt;p&gt;Spotter performs in-depth playbook analysis, ranging from best practice to deep security checks. Spotter makes sure all playbooks you run are executed securely by highlighting potential misconfigurations and security risks. It helps you understand potential outcomes when running playbooks and follow best practices to minimize security vulnerabilities and downtime.&lt;/p&gt;</description></item><item><title>Automated code review</title><link>https://steampunk.si/spotter/glossary/automated-code-review/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/automated-code-review/</guid><description>&lt;p&gt;&lt;strong&gt;Automated code review&lt;/strong&gt; is the use of tools to check code changes for bugs, security issues, style problems and policy violations without waiting for a human reviewer. Rule-based tools give the same result every time; AI code review tools use language models to comment on changes like a human reviewer would.&lt;/p&gt;
&lt;p&gt;The two types catch different things. AI reviewers are good at explaining intent, spotting logic smells and suggesting refactors, but their comments can vary and miss things. Rule-based reviewers can&amp;rsquo;t reason about intent, but they enforce a policy reliably on every change.&lt;/p&gt;</description></item><item><title>Automatically Apply Fixes</title><link>https://steampunk.si/spotter/getting-started/automatically-apply-fixes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/automatically-apply-fixes/</guid><description>&lt;p&gt;Not only does Spotter find all the errors that could seriously ruin at least your day, if not your whole infrastructure, but it can also automatically fix specific ones for you! Watch 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=ZYvTMkiEkQE"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/spotter-automatically-fix-ansible-content/"&gt;blog&lt;/a&gt;
.&lt;/p&gt;
&lt;br&gt;
&lt;figure&gt;
&lt;img alt="Reeva robot offering to rewrite and auto-fix broken playbooks in one pass" width="865" height="353.25"
 src="img-gs-reeva3.svg"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;&lt;br&gt;
&lt;p&gt;All you have to do is run the Spotter scan command with the &lt;code&gt;--rewrite&lt;/code&gt; argument and watch the magic unfold as Spotter automatically changes your Ansible content: &lt;/p&gt;</description></item><item><title>CI/CD gating</title><link>https://steampunk.si/spotter/glossary/cicd-gating/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/cicd-gating/</guid><description>&lt;p&gt;&lt;strong&gt;CI/CD gating&lt;/strong&gt; is a pipeline step that stops a change from moving forward unless it passes defined checks. A gate returns a clear pass or fail. If it fails, the merge or deployment is blocked until the code is fixed or an approved exception is recorded.&lt;/p&gt;
&lt;p&gt;Gates differ from warnings. A warning can be ignored under deadline pressure; a gate can&amp;rsquo;t. That&amp;rsquo;s why governance teams put their most important policies behind gates, such as no deprecated modules, no hardcoded credentials and no unapproved Terraform providers.&lt;/p&gt;</description></item><item><title>CI/CD security</title><link>https://steampunk.si/spotter/glossary/cicd-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/cicd-security/</guid><description>&lt;p&gt;&lt;strong&gt;CI/CD security&lt;/strong&gt; covers two things: protecting the pipeline itself, and using the pipeline to enforce security on the code that passes through it. A secure pipeline controls who can change it, keeps its secrets safe, and blocks code that fails security or policy checks.&lt;/p&gt;
&lt;p&gt;The second part is where infrastructure code governance fits. Ansible Playbooks and Terraform plans change real systems, so the pipeline should verify them before any deployment step. Steampunk Spotter runs as a part of CICD and fails the job when a Playbook or plan breaks a policy.&lt;/p&gt;</description></item><item><title>CIS Benchmark</title><link>https://steampunk.si/spotter/glossary/cis-benchmark/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/cis-benchmark/</guid><description>&lt;p&gt;A &lt;strong&gt;CIS Benchmark&lt;/strong&gt; is a consensus-based set of secure configuration guidelines published by the Center for Internet Security (CIS). Benchmarks exist for operating systems, cloud platforms, databases and other technologies. Each recommendation describes a setting, why it matters and how to check it.&lt;/p&gt;
&lt;p&gt;Auditors and security teams widely use CIS Benchmarks as a baseline, and many compliance frameworks reference them. They&amp;rsquo;re usually applied at two levels: Level 1 for practical baseline hardening, Level 2 for higher-security environments.&lt;/p&gt;</description></item><item><title>Cloud governance</title><link>https://steampunk.si/spotter/glossary/cloud-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/cloud-governance/</guid><description>&lt;p&gt;&lt;strong&gt;Cloud governance&lt;/strong&gt; is the set of policies, processes and controls an organization uses to manage cloud resources securely, compliantly and cost-effectively. It defines who can create what, how resources must be configured, how spend is controlled, and how compliance is proven.&lt;/p&gt;
&lt;p&gt;A cloud governance framework usually covers five areas: security and identity, compliance, cost management, resource configuration standards, and operations. Each needs both a written policy and a way to enforce it.&lt;/p&gt;</description></item><item><title>Compliance as code</title><link>https://steampunk.si/spotter/glossary/compliance-as-code/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/compliance-as-code/</guid><description>&lt;p&gt;&lt;strong&gt;Compliance as code&lt;/strong&gt; is the practice of turning regulatory and industry requirements, such as CIS Benchmarks, PCI DSS or internal audit controls, into automated checks. Each control maps to one or more rules that run against code and systems, producing continuous, repeatable evidence instead of manual audit spreadsheets.&lt;/p&gt;
&lt;p&gt;Compliance as code builds on policy as code. The difference is the source of the rules: policy as code covers any rule, while compliance as code maps rules to external frameworks and keeps the mapping for auditors.&lt;/p&gt;</description></item><item><title>Configuration drift</title><link>https://steampunk.si/spotter/glossary/configuration-drift/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/configuration-drift/</guid><description>&lt;p&gt;&lt;strong&gt;Configuration drift&lt;/strong&gt; is the gradual divergence between the configuration a system should have, as defined in code, and the configuration it actually has. It happens when people make manual changes, hotfixes aren&amp;rsquo;t written back to code, or automation runs inconsistently across environments.&lt;/p&gt;
&lt;p&gt;Drift causes &amp;ldquo;works in staging, fails in production&amp;rdquo; incidents, security gaps and failed audits. It also makes the next automated change risky, because the code no longer describes reality.&lt;/p&gt;</description></item><item><title>Create Custom Policies</title><link>https://steampunk.si/spotter/getting-started/create-custom-policies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/create-custom-policies/</guid><description>&lt;p&gt;To boost security, ensure compliance, and customize Spotter to meet your unique requirements, you can create custom policies to enforce regulations, establish playbook standards, define modules and collections, enforce naming conventions, limit required values on specific modules, and much more. Watch 
&lt;a target="_blank" rel="noopener noreferrer" href="https://youtu.be/BebTzyg2QYA?si=wh3DjrKb1y7mrxjr"&gt;DEMO&lt;/a&gt;
.&lt;/p&gt;
&lt;br&gt;
&lt;figure&gt;
&lt;img alt="Spotter robot Rulus saying: Define your rules; I make sure every playbook obeys them" width="865" height="352.64"
 src="img-gs-rulus3.svg"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;&lt;br&gt;&lt;br&gt;
&lt;h3 aria-level="2" id="Write-Custom-Policies" class="pt-30"&gt; Write Custom Policies &lt;/h3&gt;
&lt;p&gt;Spotter uses 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.openpolicyagent.org/docs/latest/"&gt;Open Policy Agent (OPA) &lt;/a&gt;
 to define Custom policies. These policies are written in a human-readable format using the Rego language. You don’t need to know any programming language to write them, you just need to understand how to write Rego files.&lt;/p&gt;</description></item><item><title>Create Your Account</title><link>https://steampunk.si/spotter/getting-started/create-your-account/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/create-your-account/</guid><description>&lt;p&gt;To start using Steampunk Spotter, head over to the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/register/team-plan"&gt;registration page&lt;/a&gt;
, sign up for an account and verify your email.&lt;br&gt;&lt;br&gt;&lt;/p&gt;
&lt;figure&gt;
 &lt;img width="1920" height="1080" class="zoom-image" src="https://steampunk.si/images/spotter/getting-started/img_gs_create_your_account.svg" alt="registration.svg" /&gt;
 &lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;</description></item><item><title>Day 2 operations</title><link>https://steampunk.si/spotter/glossary/day-2-operations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/day-2-operations/</guid><description>&lt;p&gt;&lt;strong&gt;Day 2 operations&lt;/strong&gt; are everything that happens after a system is deployed: patching, upgrades, scaling, configuration changes, backup, monitoring and compliance. Day 0 is design, Day 1 is the initial deployment, and Day 2 lasts for the rest of the system&amp;rsquo;s life.&lt;/p&gt;
&lt;p&gt;Most automation effort is spent on Day 2, and that&amp;rsquo;s where Ansible is used most. Teams change configuration across thousands of hosts, upgrade platforms and roll out security fixes, often under time pressure.&lt;/p&gt;</description></item><item><title>Define your custom rules and policies</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description>&lt;pre&gt;&amp;gt; spotter policies set Policies
Custom policies successfully set.
 &amp;gt; spotter scan playbook.yml
Scanning...success. &lt;font color="#56C285"&gt;━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━&lt;/font&gt; &lt;font color="#56C285"&gt;100%&lt;/font&gt; 0:00:00

&lt;b&gt;Check results&lt;/b&gt;:
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300]&lt;/font&gt; Name value should start with uppercase letter.
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300]&lt;/font&gt; Region should be set to europe (eu-...).
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300::IncorrectValue]&lt;/font&gt; ec2_group.rules[0] SSH&amp;apos; (Port:22) should not be public.
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300::IncorrectValue]&lt;/font&gt; ec2_group.rules[1] should not open the http port (80).
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Instances should not be in default security groups.
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Name value should end with a dot.
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Volume size should be set to less then 128GB.
&lt;font color="#F66151"&gt;playbook.yml:41:7: ERROR: [E2300]&lt;/font&gt; Name value should end with a dot.
playbook.yml:47:7: HINT: [H1600] Tasks should always be named using the name parameter.
&lt;font color="#F66151"&gt;playbook.yml:52:7: ERROR: [E2300]&lt;/font&gt; Access key should be written as a variable.

&lt;b&gt;Scan summary&lt;/b&gt;:
Spotter took &lt;b&gt;2.078 s&lt;/b&gt; to scan your input.
It resulted in &lt;font color="#F66151"&gt;&lt;b&gt;9 error(s)&lt;/b&gt;&lt;/font&gt;, &lt;font color="#E9AD0C"&gt;&lt;b&gt;0 warning(s)&lt;/b&gt;&lt;/font&gt; and &lt;b&gt;1 hint(s)&lt;/b&gt;.
Can &lt;font color="#C061CB"&gt;&lt;b&gt;rewrite&lt;/b&gt;&lt;/font&gt; &lt;b&gt;0 file(s)&lt;/b&gt; with &lt;b&gt;0 change(s)&lt;/b&gt;.
Overall status: &lt;font color="#F66151"&gt;&lt;b&gt;ERROR&lt;/b&gt;&lt;/font&gt;

&amp;gt; spotter clear-policies
Custom policies successfully cleared.
&amp;gt; 
&lt;/pre&gt;</description></item><item><title>Deprecated module (Ansible)</title><link>https://steampunk.si/spotter/glossary/ansible-deprecated-module/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-deprecated-module/</guid><description>&lt;p&gt;A &lt;strong&gt;deprecated module&lt;/strong&gt; is an Ansible module that has been marked for removal in a future ansible-core or Collection release. Ansible prints a deprecation warning when a Playbook uses it, naming the version in which it will be removed and, usually, its replacement.&lt;/p&gt;
&lt;p&gt;Deprecation warnings are easy to ignore because the Playbook still works. Then the removal version ships, and the Playbook fails during an upgrade or a migration to Red Hat AAP. Deprecated arguments and changed defaults cause the same problem in a less visible way.&lt;/p&gt;</description></item><item><title>Deterministic vs probabilistic verification</title><link>https://steampunk.si/spotter/glossary/deterministic-vs-probabilistic-verification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/deterministic-vs-probabilistic-verification/</guid><description>&lt;p&gt;&lt;strong&gt;Deterministic verification&lt;/strong&gt; applies fixed rules, so the same code always gets the same pass or fail result. &lt;strong&gt;Probabilistic verification&lt;/strong&gt; uses a model, such as an LLM, that predicts whether code looks correct. Its answers can vary between runs and can be confidently wrong.&lt;/p&gt;
&lt;p&gt;AI coding assistants are probabilistic. They&amp;rsquo;re useful for writing Ansible and Terraform code quickly, but they don&amp;rsquo;t know your organization&amp;rsquo;s policies. They can suggest deprecated modules or provider versions, and they can&amp;rsquo;t confirm that a change is safe for your existing state.&lt;/p&gt;</description></item><item><title>DevOps pipeline</title><link>https://steampunk.si/spotter/glossary/devops-pipeline/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/devops-pipeline/</guid><description>&lt;p&gt;A &lt;strong&gt;DevOps pipeline&lt;/strong&gt; is the automated sequence of steps that takes a code change from commit to production. It usually covers build, test, security and policy checks, packaging and deployment. Each step runs automatically, and a change moves forward only when the previous step passes.&lt;/p&gt;
&lt;p&gt;Common stages are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Commit: a developer pushes code and opens a merge request.&lt;/li&gt;
&lt;li&gt;Build and test: the pipeline compiles code and runs unit tests.&lt;/li&gt;
&lt;li&gt;Verify: security, compliance and policy checks run, including checks on infrastructure code.&lt;/li&gt;
&lt;li&gt;Release: approved artifacts are versioned and stored.&lt;/li&gt;
&lt;li&gt;Deploy: an execution platform applies the change to real infrastructure.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;For infrastructure as code, the verify stage is where Ansible Playbooks and Terraform plans should be checked. Steampunk Spotter sits in that stage. Execution platforms handle the deploy stage.&lt;/p&gt;</description></item><item><title>DevSecOps</title><link>https://steampunk.si/spotter/glossary/devsecops/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/devsecops/</guid><description>&lt;p&gt;&lt;strong&gt;DevSecOps&lt;/strong&gt; is an approach that makes security a shared responsibility across development, security and operations teams. Security checks are automated and built into the delivery pipeline, so every change is tested for vulnerabilities and policy violations as part of normal work, not in a separate review at the end.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;DevSecOps vs DevOps.&lt;/strong&gt; DevOps joins development and operations to ship faster and more reliably. DevSecOps adds security to that loop as an equal owner, with security checks automated in the same pipeline. The goal is to keep the speed of DevOps without accepting more risk.&lt;/p&gt;</description></item><item><title>Easily upgrade to the latest Ansible version</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description>&lt;pre&gt; &amp;gt; spotter set-policies Policies
Custom policies successfully set.
 &amp;gt; spotter scan playbook.yml
Scanning...success. &lt;font color="#56C285"&gt;━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━&lt;/font&gt; &lt;font color="#56C285"&gt;100%&lt;/font&gt; 0:00:00

&lt;b&gt;Check results&lt;/b&gt;:
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300]&lt;/font&gt; Name value should start with uppercase letter.
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300]&lt;/font&gt; Region should be set to europe (eu-...).
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300::IncorrectValue]&lt;/font&gt; ec2_group.rules[0] SSH&amp;apos; (Port:22) should not be public.
&lt;font color="#F66151"&gt;playbook.yml:7:7: ERROR: [E2300::IncorrectValue]&lt;/font&gt; ec2_group.rules[1] should not open the http port (80).
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Instances should not be in default security groups.
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Name value should end with a dot.
&lt;font color="#F66151"&gt;playbook.yml:23:7: ERROR: [E2300]&lt;/font&gt; Volume size should be set to less then 128GB.
&lt;font color="#F66151"&gt;playbook.yml:41:7: ERROR: [E2300]&lt;/font&gt; Name value should end with a dot.
playbook.yml:47:7: HINT: [H1600] Tasks should always be named using the name parameter.
&lt;font color="#F66151"&gt;playbook.yml:52:7: ERROR: [E2300]&lt;/font&gt; Access key should be written as a variable.

&lt;b&gt;Scan summary&lt;/b&gt;:
Spotter took &lt;b&gt;2.078 s&lt;/b&gt; to scan your input.
It resulted in &lt;font color="#F66151"&gt;&lt;b&gt;9 error(s)&lt;/b&gt;&lt;/font&gt;, &lt;font color="#E9AD0C"&gt;&lt;b&gt;0 warning(s)&lt;/b&gt;&lt;/font&gt; and &lt;b&gt;1 hint(s)&lt;/b&gt;.
Can &lt;font color="#C061CB"&gt;&lt;b&gt;rewrite&lt;/b&gt;&lt;/font&gt; &lt;b&gt;0 file(s)&lt;/b&gt; with &lt;b&gt;0 change(s)&lt;/b&gt;.
Overall status: &lt;font color="#F66151"&gt;&lt;b&gt;ERROR&lt;/b&gt;&lt;/font&gt;

 &amp;gt; spotter clear-policies
Custom policies successfully cleared.
 &amp;gt; 

&lt;/pre&gt;</description></item><item><title>Fix issues automatically</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description>&lt;pre&gt;
&gt; spotter scan --rewrite playbook.yml
&lt;span class="error"&gt;playbook.yml:5:7&lt;/span&gt;: ERROR: Use a fully-qualified name, such as &lt;span class="error"&gt;community.crypto.x509_certificate&lt;/span&gt; instead of &lt;span class="error"&gt;openssl_certificate&lt;/span&gt;.
View docs at https://docs.steampunk.si/plugins/community/crypto/latest/module/x509_certificate.html.
playbook.yml:5:7: HINT Required collection community.crypto is missing from requirements.yml or requirements.yml is missing.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Overall status: ERROR 
&gt; cat playbook.yml
---
- name: Sample playbook
 hosts: localhost
 tasks:
 - name: Ensure that the server certificate belongs to the specified
 private key community.crypto.x509_certificate:
 path: “&amp;#123;&amp;#123; config_path &amp;#125;&amp;#125;/certificates/server.crt”
 privatekey_path: “&amp;#123;&amp;#123; config_path &amp;#125;&amp;#125;/certificates/server.key”
 provider: assertonly
&gt;
&lt;/pre&gt;</description></item><item><title>FQCN (fully qualified collection name)</title><link>https://steampunk.si/spotter/glossary/ansible-fqcn/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/ansible-fqcn/</guid><description>&lt;p&gt;A &lt;strong&gt;fully qualified collection name (FQCN)&lt;/strong&gt; is the complete name of an Ansible module, plugin or role, in the form &lt;code&gt;namespace.collection.name&lt;/code&gt;. For example, &lt;code&gt;ansible.builtin.copy&lt;/code&gt; is the FQCN of the copy module. Using FQCNs tells Ansible exactly which Collection&amp;rsquo;s code to run.&lt;/p&gt;
&lt;p&gt;Short names such as &lt;code&gt;copy&lt;/code&gt; still work in many cases, but they can resolve to the wrong module when two Collections define the same name. FQCNs remove that ambiguity, make Playbooks easier to review and are required by many style guides.&lt;/p&gt;</description></item><item><title>From Risk to Resilience: An Enterprise Story to Secure and Compliant Ansible Playbooks | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/security-compliance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/security-compliance/</guid><description>&lt;p&gt;As Ansible Playbooks become increasingly complex and distributed across multiple teams, securing them becomes a critical challenge. Enterprises are under constant pressure from evolving cyber threats, software vulnerabilities and more complex compliance requirements. Without the right controls in place, organizations risk exposing security gaps, failing to meet compliance requirements and making costly mistakes. Relying on manual controls and reactive measures is no longer enough. Security and compliance must be integrated directly into automation pipelines.&lt;/p&gt;</description></item><item><title>Generate missing requirements files</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description>&lt;pre&gt;&amp;gt; ls
playbook.yml
&amp;gt; spotter scan --rewrite playbook.yml
Scanning...success. &lt;font color="#56C285"&gt;━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━&lt;/font&gt; &lt;font color="#56C285"&gt;100%&lt;/font&gt; 0:00:00

&lt;b&gt;Rewritten check results&lt;/b&gt;:
playbook.yml:5:7: HINT: [H1900] Required collection &lt;b&gt;community.crypto&lt;/b&gt; is missing from requirements.yml or requirements.yml is missing.

&lt;b&gt;Remaining check results&lt;/b&gt;:
&lt;font color="#F66151"&gt;playbook.yml:5:7: ERROR: [E601]&lt;/font&gt; Value of &lt;font color="#F66151"&gt;&lt;b&gt;provider&lt;/b&gt;&lt;/font&gt; in module &lt;font color="#F66151"&gt;&lt;b&gt;community.crypto.x509_certificate&lt;/b&gt;&lt;/font&gt; is set to &lt;font color="#F66151"&gt;&lt;b&gt;assertonly&lt;/b&gt;&lt;/font&gt; which does not match any of the possible choices listed in [&lt;font color="#F66151"&gt;&lt;b&gt;acme&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;entrust&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;ownca&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;selfsigned&lt;/b&gt;&lt;/font&gt;]. View docs at &lt;font color="#2AA1B3"&gt;https://docs.steampunk.si/plugins/community/crypto/2.15.1/module/x509_certificate.html&lt;/font&gt;.

&lt;b&gt;Scan summary&lt;/b&gt;:
Spotter took &lt;b&gt;1.368 s&lt;/b&gt; to scan your input.
It resulted in &lt;font color="#F66151"&gt;&lt;b&gt;1 error(s)&lt;/b&gt;&lt;/font&gt;, &lt;font color="#E9AD0C"&gt;&lt;b&gt;0 warning(s)&lt;/b&gt;&lt;/font&gt; and &lt;b&gt;1 hint(s)&lt;/b&gt;.
Did &lt;font color="#C061CB"&gt;&lt;b&gt;rewrite&lt;/b&gt;&lt;/font&gt; &lt;b&gt;1 file(s)&lt;/b&gt; with &lt;b&gt;1 change(s)&lt;/b&gt;.
Overall status: &lt;font color="#F66151"&gt;&lt;b&gt;ERROR&lt;/b&gt;&lt;/font&gt;
&amp;gt; ls
playbook.yml requirements.yml
&amp;gt; 

&lt;/pre&gt;</description></item><item><title>Generative AI governance</title><link>https://steampunk.si/spotter/glossary/generative-ai-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/generative-ai-governance/</guid><description>&lt;p&gt;&lt;strong&gt;Generative AI governance&lt;/strong&gt; is the framework of policies, roles and controls an organization uses to manage how generative AI tools are adopted and used. It covers acceptable use, data protection, model and vendor approval, output review, accountability, and compliance with regulations.&lt;/p&gt;
&lt;p&gt;Most frameworks address four questions: which tools are approved, what data can be shared with them, who is accountable for their output, and how that output is checked before it&amp;rsquo;s used.&lt;/p&gt;</description></item><item><title>Get instant help with module documentation</title><link/><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid/><description>&lt;pre&gt; &amp;gt; spotter scan playbook.yml
Scanning...success. &lt;font color="#56C285"&gt;━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━&lt;/font&gt; &lt;font color="#56C285"&gt;100%&lt;/font&gt; 0:00:00

&lt;b&gt;Check results&lt;/b&gt;:
&lt;font color="#F66151"&gt;playbook.yml:5:7: ERROR: [E006]&lt;/font&gt; Required parameter &lt;font color="#F66151"&gt;&lt;b&gt;instance.host&lt;/b&gt;&lt;/font&gt; was not set in module &lt;font color="#F66151"&gt;&lt;b&gt;servicenow.itsm.change_request&lt;/b&gt;&lt;/font&gt;. Environment fallback was unsuccessful as variable &lt;font color="#F66151"&gt;&lt;b&gt;SN_HOST&lt;/b&gt;&lt;/font&gt; is not set. If you decide to set the environment variable remember to do it on other configuration systems too. Another way is to set the parameter in task directly. View docs at &lt;font color="#2AA1B3"&gt;https://docs.steampunk.si/plugins/servicenow/itsm/2.2.0/module/change_request.html&lt;/font&gt;.
&lt;font color="#F66151"&gt;playbook.yml:18:7: ERROR: [E601]&lt;/font&gt; Value of &lt;font color="#F66151"&gt;&lt;b&gt;policy&lt;/b&gt;&lt;/font&gt; in module &lt;font color="#F66151"&gt;&lt;b&gt;ansible.builtin.iptables&lt;/b&gt;&lt;/font&gt; is set to &lt;font color="#F66151"&gt;&lt;b&gt;DROPcy=DROP chain=INPUT&lt;/b&gt;&lt;/font&gt; which does not match any of the possible choices listed in [&lt;font color="#F66151"&gt;&lt;b&gt;ACCEPT&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;DROP&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;QUEUE&lt;/b&gt;&lt;/font&gt;, &lt;font color="#F66151"&gt;&lt;b&gt;RETURN&lt;/b&gt;&lt;/font&gt;].

&lt;b&gt;Scan summary&lt;/b&gt;:
Spotter took &lt;b&gt;2.005 s&lt;/b&gt; to scan your input.
It resulted in &lt;font color="#F66151"&gt;&lt;b&gt;2 error(s)&lt;/b&gt;&lt;/font&gt;, &lt;font color="#E9AD0C"&gt;&lt;b&gt;0 warning(s)&lt;/b&gt;&lt;/font&gt; and &lt;b&gt;0 hint(s)&lt;/b&gt;.
Can &lt;font color="#C061CB"&gt;&lt;b&gt;rewrite&lt;/b&gt;&lt;/font&gt; &lt;b&gt;0 file(s)&lt;/b&gt; with &lt;b&gt;0 change(s)&lt;/b&gt;.
Overall status: &lt;font color="#F66151"&gt;&lt;b&gt;ERROR&lt;/b&gt;&lt;/font&gt;
 &amp;gt; 
&lt;/pre&gt;</description></item><item><title>HashiCorp Sentinel</title><link>https://steampunk.si/spotter/glossary/hashicorp-sentinel/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/hashicorp-sentinel/</guid><description>&lt;p&gt;&lt;strong&gt;HashiCorp Sentinel&lt;/strong&gt; is a policy-as-code framework built into HashiCorp&amp;rsquo;s commercial products, including HCP Terraform and Terraform Enterprise. Sentinel policies run between &lt;code&gt;terraform plan&lt;/code&gt; and &lt;code&gt;terraform apply&lt;/code&gt;, and can block an apply that violates a rule, such as an unapproved instance type or missing tags.&lt;/p&gt;
&lt;p&gt;Sentinel uses its own policy language and supports enforcement levels: advisory, soft-mandatory (can be overridden) and hard-mandatory. Because it runs inside HashiCorp&amp;rsquo;s platform, it applies only to Terraform runs managed there.&lt;/p&gt;</description></item><item><title>How an Enterprise Company Saved Over 17,000 Hours with Automated Ansible Upgrade and Migration | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/upgrade-and-migration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/upgrade-and-migration/</guid><description>&lt;p&gt;Enterprises with critical infrastructure face unique challenges when migrating from legacy platforms like AWX or Tower. Playbooks are often outdated, inconsistent and spread across multiple teams. Combined with strict compliance rules, this makes modernizing playbooks difficult and time-consuming. For this reason, many enterprises are turning to automation — to speed up the process, reduce manual effort and lower the risk of errors.&lt;/p&gt;
&lt;p&gt;In this webinar we show you a real-life example of how one of the world’s largest financial institutions migrated thousands of legacy Ansible playbooks to the Red Hat Ansible Automation Platform (AAP) 2.4 while also upgrading from Ansible 2.9 to 2.15 to deliver fully AAP-compliant playbooks in just three months.&lt;/p&gt;</description></item><item><title>How Computer Space Leverages Steampunk Spotter to Supercharge Productivity</title><link>https://steampunk.si/spotter/customer-stories/computer-space/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/customer-stories/computer-space/</guid><description>&lt;figure class="quote"&gt;
"Spotter &lt;b&gt;transforms our automation process&lt;/b&gt; by identifying and mitigating potential issues before execution, 
reducing errors, and boosting productivity. &lt;b&gt;It's not just a tool – it's a catalyst for evolving the way we manage 
and perceive automation.&lt;/b&gt;"
&lt;figure class="signature"&gt;
&lt;b&gt;Miguel Esteban,&lt;/b&gt; CEO, Computer Space
&lt;/figure&gt;
&lt;/figure&gt;
&lt;h3 id="challenge"&gt;Challenge&lt;/h3&gt;
&lt;p&gt;Computer Space is committed to enhancing its services by establishing an Automation Office. However,
the complexity of Ansible Playbooks and the need for manual review posed challenges for the company.
As a result, achieving certain milestones, such as Ansible upgrades and implementing custom policies,
became difficult.&lt;/p&gt;</description></item><item><title>How Spotter enabled Computer Space to scale its Ansible automation projects and create a centralized quality framework</title><link>https://steampunk.si/spotter/customer-stories/computer-space-automation-scaling/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/customer-stories/computer-space-automation-scaling/</guid><description>&lt;h3 id="the-challenge"&gt;The Challenge&lt;/h3&gt;
&lt;p&gt;With nearly 600 Ansible Playbooks spread across 20–25 repositories, Computer Space faced a challenge of &lt;strong&gt;how to maintain code quality and standardization&lt;/strong&gt;. Teams with varying levels of expertise contributed to the codebase, leading to inconsistent implementations and bottlenecks in manual reviews. Maintaining best practices was time-consuming, error-prone, and unsustainable. It became clear that further scaling without a robust quality control system would introduce unacceptable risks. A more standardized approach was essential.&lt;/p&gt;</description></item><item><title>IaC scanning</title><link>https://steampunk.si/spotter/glossary/iac-scanning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/iac-scanning/</guid><description>&lt;p&gt;&lt;strong&gt;IaC scanning&lt;/strong&gt; is the automated analysis of infrastructure as code files, such as Terraform, Ansible, CloudFormation or Kubernetes manifests, to find misconfigurations, security risks and policy violations. Scanners read the code without deploying it and report each finding with its location and severity.&lt;/p&gt;
&lt;p&gt;Scanners run in three places: the editor for instant feedback, pre-commit hooks, and CI/CD pipelines. In CI/CD, results can fail the build so risky code isn&amp;rsquo;t merged.&lt;/p&gt;</description></item><item><title>IaC security</title><link>https://steampunk.si/spotter/glossary/iac-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/iac-security/</guid><description>&lt;p&gt;&lt;strong&gt;IaC security&lt;/strong&gt; is the practice of finding and preventing security problems in infrastructure as code before it&amp;rsquo;s deployed. It checks templates, Playbooks and plans for misconfigurations, exposed secrets, insecure defaults and vulnerable components, so insecure infrastructure is never created in the first place.&lt;/p&gt;
&lt;p&gt;Common IaC security issues include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Open network rules, such as security groups allowing 0.0.0.0/0 on admin ports.&lt;/li&gt;
&lt;li&gt;Hardcoded passwords, tokens and keys.&lt;/li&gt;
&lt;li&gt;Disabled encryption or logging on storage and databases.&lt;/li&gt;
&lt;li&gt;Overly broad permissions on IAM roles or service accounts.&lt;/li&gt;
&lt;li&gt;Outdated modules, Collections or providers with known CVEs.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;IaC security best practices:&lt;/strong&gt; check code at commit and in CI/CD, not after deployment; store secrets in a vault; pin module, Collection and provider versions; apply CIS Benchmarks as policy; and block merges on critical findings.&lt;/p&gt;</description></item><item><title>Infrastructure as code (IaC)</title><link>https://steampunk.si/spotter/glossary/infrastructure-as-code/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/infrastructure-as-code/</guid><description>&lt;p&gt;&lt;strong&gt;Infrastructure as code (IaC)&lt;/strong&gt; is the practice of defining and managing servers, networks, cloud resources and configuration in machine-readable files instead of manual setup. The files are versioned, reviewed and applied by automation tools, so every environment can be rebuilt the same way, every time.&lt;/p&gt;
&lt;p&gt;IaC tools fall into two broad styles. Declarative tools such as Terraform describe the end state, and the tool works out the steps. Configuration management tools such as Ansible describe tasks that bring systems into the desired state. Many teams use both: Terraform to provision cloud resources and Ansible to configure them.&lt;/p&gt;</description></item><item><title>Infrastructure as code governance</title><link>https://steampunk.si/spotter/glossary/iac-governance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/iac-governance/</guid><description>&lt;p&gt;&lt;strong&gt;Infrastructure as code governance&lt;/strong&gt; is the practice of enforcing an organization&amp;rsquo;s policies on automation code, such as Ansible Playbooks and Terraform plans, before that code is executed. Governance checks run at commit and in CI/CD, so policy violations, deprecated modules and breaking changes are caught before they reach production.&lt;/p&gt;
&lt;p&gt;Governance is broader than security scanning. It covers security rules, but also internal standards (approved modules and providers, naming, tagging), compliance frameworks such as CIS Benchmarks, and version compatibility. It also produces evidence: a record of which code passed which checks and when.&lt;/p&gt;</description></item><item><title>Install Spotter CLI</title><link>https://steampunk.si/spotter/getting-started/install-spotter-cli/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/install-spotter-cli/</guid><description>&lt;p&gt;Spotter CLI is easy to use and install. It’s available as a 
&lt;a target="_blank" rel="noopener noreferrer" href="https://pypi.org/project/steampunk-spotter/"&gt;steampunk-spotter&lt;/a&gt;
 Python package, but you will need at least Python 3 to install it.&lt;/p&gt;
&lt;div class="copy-code"&gt;
 &lt;div class="copy-code-inner"&gt;
 &lt;span class="pl-2"&gt;$&lt;/span&gt;
 &lt;code class="copied-text"&gt;pip install steampunk-spotter&lt;/code&gt;
 &lt;span class="copied"&gt;Copied!&lt;/span&gt;
 &lt;/div&gt;
&lt;/div&gt;
&lt;br/&gt;
&lt;p&gt;Once you&amp;rsquo;ve got the CLI up and running, you can easily check out its commands and optional arguments. Just type in &lt;code&gt;spotter –help&lt;/code&gt; to see all the info you need. And remember, you can use &lt;code&gt;--help or –h&lt;/code&gt; with any command too. Just type in &lt;code&gt;spotter –help/-h &amp;lt; your command&amp;gt;&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Integrations</title><link>https://steampunk.si/spotter/getting-started/integrations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/integrations/</guid><description>&lt;p&gt;Boost Spotter capabilities, streamline workflows, and efficiently manage development projects. Spotter seamlessly integrates with your work environment. Include it into your CI/CD pipelines with GitLab and GitHub integration or use it with your favorite code editor with Spotter Visual Studio Code extension - and even discover additional functionalities. No matter where you do your best work, Spotter is right by your side.&lt;/p&gt;
&lt;h2 id="github-actions"&gt;GitHub Actions &lt;/h2&gt;
&lt;p&gt;The Steampunk Spotter GitHub Action makes it easy to scan your Ansible content right within your GitHub CI/CD workflows. See 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=-PGJ09oN_PM&amp;amp;t=4s"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/spotter-github-actions/"&gt;tutorial&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Let your AI agent write Ansible and Terraform code you can trust</title><link>https://steampunk.si/spotter/mcp-early-access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/mcp-early-access/</guid><description>&lt;h3 id="how-it-works"&gt;How it works&lt;/h3&gt;
&lt;/br&gt;
&lt;p&gt;&lt;strong&gt;1. Request the plugin.&lt;/strong&gt; Fill in the form and we’ll reach out to you with next steps.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Install the plugin.&lt;/strong&gt; Add it to Claude Code,GitHub Copilot or others with /plugin install, and your agent starts scanning its own work.&lt;/p&gt;
&lt;figure class="benefits"&gt;
&lt;h4 aria-level="3" id="why-spotter-mcp"&gt;Why Spotter MCP:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Your policies, applied as the code is written.&lt;span class='text-normal'&gt;The agent checks its code against the same profiles and policies your team already uses.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Guardrails that keep the agent honest.&lt;span class='text-normal'&gt;It won’t skip a check to force a pass or edit files outside its task.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;Fast and focused results.&lt;span class='text-normal'&gt;Compact output, ordered by severity, keeps every check quick and light on tokens.&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/figure&gt;</description></item><item><title>Live Demo: Securing Ansible Workflows with Steampunk Spotter | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/live-demo-securing-ansible-workflows-with-steampunk-spotter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/live-demo-securing-ansible-workflows-with-steampunk-spotter/</guid><description>&lt;p&gt;Most security incidents don’t start with a sophisticated attack. They start with a &lt;strong&gt;hardcoded secret, an outdated dependency, or a misconfigured playbook that nobody caught.&lt;/strong&gt; As Ansible environments grow more complex and span multiple teams, these risks multiply — and manual controls just can&amp;rsquo;t keep up. The pattern is always the same: risks that were invisible during development become very visible in production at a much higher price.&lt;/p&gt;
&lt;p&gt;Our experts will show you how Steampunk Spotter catches and addresses these risks before it’s too late - through a live demo of its core security capabilities. Then we&amp;rsquo;ll walk through a real enterprise case study so you can see what this looks like in a highly regulated environment.&lt;/p&gt;</description></item><item><title>Manage Supply Chain</title><link>https://steampunk.si/spotter/getting-started/manage-supply-chain/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/manage-supply-chain/</guid><description>&lt;p&gt;Maintain strict control over the Ansible content used in your automation playbooks. Ensure that automation dependencies, such as Ansible runtime and Ansible Collection versions, comply with your security and compliance policies. Spotter allows security teams to approve safe versions and block vulnerable or unapproved software, while playbook writers focus on automation logic without needing deep Python expertise. 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/spotter/blog/how-to-ensure-only-secure-and-approved-ansible-content/"&gt;Read blog&lt;/a&gt;
 or 
&lt;a target="_blank" rel="noopener noreferrer" href="https://youtu.be/yebz6d3Ncmk?si=ggLXCEV91NzZKnBW"&gt;watch DEMO.&lt;/a&gt;
&lt;/p&gt;
&lt;br&gt;
&lt;figure&gt;
&lt;img alt="McChain machine illustration: keep your supply chain healthy by vetting collections" width="865" height="352.92"
 src="img-gs-mcchain3.svg"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;&lt;br&gt;
&lt;p&gt;To manage the supply chain, visit Spotter App and add or remove constraints with a few simple clicks.&lt;/p&gt;</description></item><item><title>MindPoint Group and XLAB Steampunk Join Forces for Enhanced Security Compliance Automation</title><link>https://steampunk.si/spotter/customer-stories/mindpoint-group/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/customer-stories/mindpoint-group/</guid><description>&lt;figure&gt;
&lt;img
 loading="lazy"
 width="798" height="473.579"
 alt="dashboard"
 src="dashboard.svg"
/&gt;
&lt;/figure&gt; 
&lt;h3 id="challenge"&gt;Challenge&lt;/h3&gt;
&lt;p&gt;Automating system security requirements can be difficult and time-consuming. &lt;strong&gt;MindPoint Group&lt;/strong&gt; solves this issue with Ansible Lockdown, a library of Ansible automation content for
hardening common operating systems, applications, and network devices and clouds, helping organizations achieve recognized security benchmark compliance
for &lt;strong&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.cisecurity.org/"&gt;CIS&lt;/a&gt;
&lt;/strong&gt; (Center for Internet Security) or &lt;strong&gt;
&lt;a target="_blank" rel="noopener noreferrer" href="https://public.cyber.mil/stigs/"&gt;STIG&lt;/a&gt;
&lt;/strong&gt; (Secure Technical Implementation Guides).&lt;/p&gt;
&lt;p&gt;While Ansible Lockdown represents a comprehensive collection of Ansible content developed and maintained &lt;strong&gt;by
expert-level cybersecurity and Ansible professionals&lt;/strong&gt;, even expert-maintained content demands continuous refinement and tuning.&lt;/p&gt;</description></item><item><title>Open Policy Agent (OPA)</title><link>https://steampunk.si/spotter/glossary/open-policy-agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/open-policy-agent/</guid><description>&lt;p&gt;&lt;strong&gt;Open Policy Agent (OPA)&lt;/strong&gt; is an open source, general-purpose policy engine and a graduated Cloud Native Computing Foundation (CNCF) project. Policies are written in a language called Rego, and OPA evaluates them against structured input, such as a Terraform plan in JSON or a Kubernetes manifest.&lt;/p&gt;
&lt;p&gt;OPA is used for Kubernetes admission control (through Gatekeeper), API authorization and infrastructure code checks. Conftest, a related tool, applies Rego policies to configuration files in CI/CD.&lt;/p&gt;</description></item><item><title>Optimizing Ansible Playbooks with Steampunk Spotter | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/optimizing-ansible-playbooks-deutsche-telekom/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/optimizing-ansible-playbooks-deutsche-telekom/</guid><description>&lt;p&gt;We’ll explore unique challenges faced by multiple teams using Ansible for varied customer projects, focusing on duplication and maintenance of roles and collections.
You’ll learn how Steampunk Spotter is being employed as a centralized platform to manage roles and collections, providing a cohesive solution for version control, security compliance,
and security audits in Ansible deployments and how it facilitates these checks to bolster security standards.&lt;/p&gt;
&lt;p&gt;We’ll also talk about the development of a compliance baseline for
Ansible Playbooks and showcase how Deutsche Telekom MMS pioneers custom policy development and compliance strategies, setting the standard for effective playbook management.&lt;/p&gt;</description></item><item><title>Policy as code</title><link>https://steampunk.si/spotter/glossary/policy-as-code/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/policy-as-code/</guid><description>&lt;p&gt;&lt;strong&gt;Policy as code&lt;/strong&gt; is the practice of writing organizational rules, such as security, compliance and operational standards, as machine-readable code. The policies are versioned in Git, reviewed like any other change, and enforced automatically by tools, so every piece of code is checked against the same rules.&lt;/p&gt;
&lt;p&gt;Without policy as code, rules live in wiki pages and reviewers&amp;rsquo; heads. They&amp;rsquo;re enforced inconsistently and are hard to audit. With it, a rule like &amp;ldquo;every S3 bucket must be encrypted&amp;rdquo; becomes a check that runs on every pull request.&lt;/p&gt;</description></item><item><title>SBOM (software bill of materials)</title><link>https://steampunk.si/spotter/glossary/sbom/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/sbom/</guid><description>&lt;p&gt;A &lt;strong&gt;software bill of materials (SBOM)&lt;/strong&gt; is a machine-readable inventory of every component in a piece of software, including libraries, packages and their versions. It lets teams see what they depend on and quickly check whether a newly disclosed vulnerability affects them. Common formats are SPDX and CycloneDX.&lt;/p&gt;
&lt;p&gt;SBOMs became a mainstream requirement after US Executive Order 14028 (2021) asked software suppliers to the federal government to provide them. Many enterprises now ask for SBOMs from every vendor.&lt;/p&gt;</description></item><item><title>Scan</title><link>https://steampunk.si/spotter/getting-started/scan/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/scan/</guid><description>&lt;p&gt;Spotter allows you to check the quality of your private Ansible content, such as tasks, playbooks, roles, and collections to improve its quality, and enables you to check the quality of public Git repositories to ensure that the resources you&amp;rsquo;re using are dependable, secure and well-maintained.
&lt;br&gt;&lt;br&gt;&lt;/p&gt;
&lt;figure&gt;
&lt;img alt="Steampunk-style machine illustration scanning Ansible content" width="865" height="352.38"
 src="img-gs-scav3.svg"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;&lt;br&gt;&lt;br&gt;
&lt;p&gt;If you want to scan private Ansible content, you can do so via Spotter CLI. All you have to do is run &lt;code&gt;spotter scan&lt;/code&gt; command, sit back and get your scan results. See 
&lt;a target="_blank" rel="noopener noreferrer" href="https://youtu.be/m88HzTXhmLs?si=ZveeTJg8OgkudYDX"&gt;DEMO&lt;/a&gt;
 or 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/blog/how-to-use-steampunk-spotter-cli-to-audit-your-playbook/"&gt;read tutorial&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Secrets detection</title><link>https://steampunk.si/spotter/glossary/secrets-detection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/secrets-detection/</guid><description>&lt;p&gt;&lt;strong&gt;Secrets detection&lt;/strong&gt; is the automated search for credentials, such as passwords, API keys, tokens and private keys, that have been written into source code, configuration files or commit history. Detection tools match known key formats and high-entropy strings, then flag or block the commit before the secret spreads.&lt;/p&gt;
&lt;p&gt;In infrastructure code, secrets often appear as default passwords in Ansible variables, provider credentials in Terraform files, or tokens pasted into a Playbook during debugging. Once pushed, a secret stays in Git history even after the line is deleted, so it must be rotated.&lt;/p&gt;</description></item><item><title>Set Scan Profiles</title><link>https://steampunk.si/spotter/getting-started/set-scan-profiles/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/set-scan-profiles/</guid><description>&lt;p&gt;When conducting scans, we target specific goals. For instance, one project might focus on upgrading our Ansible environment to a newer
version, while another could aim to enhance playbooks for the current version. This means that certain check results provided by
Steampunk Spotter may be relevant for one project but not the other. Spotter addresses this by allowing the use of scan profiles via
the &lt;code&gt;--profile&lt;/code&gt; argument - a selected set of checks. Make sure to add suitable arguments to your commands to make your scanning
experience optimal.&lt;/p&gt;</description></item><item><title>Shift left and secure: How to embed security in the Ansible development lifecycle | XLAB Steampunk</title><link>https://steampunk.si/spotter/webinars-training/shift-left-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/shift-left-security/</guid><description>&lt;p&gt;In this webinar, we will show how to embed security into the Ansible development lifecycle using a practical shift left approach, walk you through the common Ansible security risks, and share best practices for securing your Ansible automation.&lt;/p&gt;
&lt;p&gt;This session also highlights an important reality: Ansible Playbooks are only the tip of the iceberg. Every execution depends on Ansible core, collections, modules, plugins, Python packages, and system-level dependencies. Vulnerabilities anywhere in this chain can silently spread and amplify risk across your entire infrastructure. We will show you how to secure the full dependency chain, so your automation remains robust and compliant.&lt;/p&gt;</description></item><item><title>Shift-left security</title><link>https://steampunk.si/spotter/glossary/shift-left-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/shift-left-security/</guid><description>&lt;p&gt;&lt;strong&gt;Shift-left security&lt;/strong&gt; is the practice of moving security and compliance checks to the earliest stages of software delivery: the editor, the commit and the CI/CD pipeline. Instead of finding problems in production or during a late audit, teams catch them while the code is still cheap to change.&lt;/p&gt;
&lt;p&gt;The term comes from &amp;ldquo;shift-left testing,&amp;rdquo; coined by Larry Smith in 2001. Picture the delivery lifecycle as a line running left to right, from writing code to running it. Every check you move left costs less to act on, because fewer people and systems depend on the broken code.&lt;/p&gt;</description></item><item><title>Shift-left security for Terraform: Adding governance layer to your CI/CD pipeline</title><link>https://steampunk.si/spotter/webinars-training/shift-left-security-for-terraform/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/shift-left-security-for-terraform/</guid><description>&lt;p&gt;In this session, we’ll set up an enforceable policy gate on both your Terraform plan and configuration, inside the CI/CD pipeline you already run. Steampunk Spotter validates Terraform code against the current definitions of official providers. Before changes are applied, it enforces built-in checks and your own custom policies on the plan, and blocks changes that break them. You’ll see it catch secrets in cleartext, enforce an internal rule as a custom policy, and send every result to one place your security team can audit.&lt;/p&gt;</description></item><item><title>Skip and Enforce Checks</title><link>https://steampunk.si/spotter/getting-started/skip-and-enforce-checks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/skip-and-enforce-checks/</guid><description>&lt;p&gt;To help you achieve security, compliance and quality of your automation while optimizing it, Steampunk Spotter allows you to centrally control which checks to enforce or skip across your Ansible Playbooks.Watch 
&lt;a target="_blank" rel="noopener noreferrer" href="https://youtu.be/WNXuPQBWQaY"&gt;DEMO&lt;/a&gt;
 or read 
&lt;a target="_self" href="https://steampunk.si/blog/spotter-skipping-and-enforcing-checks/"&gt;blog&lt;/a&gt;
.&lt;/p&gt;
&lt;br&gt;
&lt;figure&gt;
&lt;img alt="Spotter robot Chuck saying: Let's enforce the checks that matter and skip the ones that don't" width="865" height="352.54"
 src="img-gs-chuck3.svg"
 class="zoom-image"
/&gt;
&lt;img alt="" width="30" height="30" class="zoom-overlay-image" src="https://steampunk.si/images/blog/ic-full-screen.svg"/&gt;
&lt;/figure&gt;&lt;br&gt;
&lt;h3 id="organization-level" aria-level="2"&gt;Organization Level&lt;/h3&gt;
&lt;p&gt;Organization admins can enforce or skip checks organization-wide with just a few clicks in the Spotter App. Any checks enforced at this level can’t be ignored when scanning by any user in your organization. Go to Check management, click Add rule, select whether you want to skip or enforce the check, enter the check code or search for it by name, and click Save.&lt;/p&gt;</description></item><item><title>Spotter MCP: Guardrails for AI Coding Agents writing Ansible and Terraform</title><link>https://steampunk.si/spotter/webinars-training/spotter-mcp-guardrails-for-ai-coding-agents-writing-ansible-and-terraform/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/spotter-mcp-guardrails-for-ai-coding-agents-writing-ansible-and-terraform/</guid><description>&lt;p&gt;In this live session, we’ll give the same tasks to the same AI coding agent twice: once on its own, and once with the Spotter agent plugin installed. First, you’ll see what the agent misses by itself. Then you’ll watch it find those issues, apply Spotter’s fixes and check again until the result is clean, all before the work comes back to you.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll work through three real-world tasks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Writing a new Ansible Playbook from scratch&lt;/strong&gt;, checked against your target Ansible version and policies&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrading and securing existing Playbooks&lt;/strong&gt;, starting with Spotter’s automatic fixes, then minimal changes for what’s left&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Writing a Terraform configuration&lt;/strong&gt;, checked against official provider definitions and your custom policies&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We&amp;rsquo;ll also show how the agent uses your organization&amp;rsquo;s own Spotter setup, including profiles, enforced checks and .spotter.yml, and what stops it from taking shortcuts like skipping a check just to get a passing result.&lt;/p&gt;</description></item><item><title>Steampunk Spotter Guide</title><link>https://steampunk.si/spotter/getting-started/introduction/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/introduction/</guid><description>&lt;p&gt;Steampunk Spotter thoroughly analyzes and improves your Ansible content to help you identify elusive and time-consuming errors, enhance the quality, reliability, and security of your playbooks, shorten development and testing time, and adhere to automation best practices. This powerful platform comprises a user-friendly CLI and the 
&lt;a target="_blank" rel="noopener noreferrer" href="https://spotter.steampunk.si/login"&gt;Spotter app&lt;/a&gt;
, providing insights into your automation. Moreover, Spotter seamlessly integrates with popular platforms like GitLab, GitHub, and VS Code, further enhancing its versatility and usability.&lt;/p&gt;</description></item><item><title>Streamlining Ansible Playbook Migration and Upgrade for One of the Top Global FSIs with Steampunk Spotter</title><link>https://steampunk.si/spotter/customer-stories/global-fsi-playbooks-migration-and-upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/customer-stories/global-fsi-playbooks-migration-and-upgrade/</guid><description>&lt;h3 id="challenge"&gt;Challenge&lt;/h3&gt;
&lt;p&gt;The bank had to migrate thousands of Ansible Playbooks from legacy platform to AAP 2.4 and ensure compatibility with Ansible 2.15. These playbooks were created over the course of nearly a decade and followed different patterns as Ansible evolved over time. As teams were spread around the globe, they also developed their own common practices, which resulted in the Ansible Playbooks being inconsistent. Fixing these issues manually would have required years of engineering effort for the bank, a number of highly skilled Ansible experts to understand the changes required, and would have been a major obstacle to modernization, automation scaling, and operational efficiency.&lt;/p&gt;</description></item><item><title>Terraform</title><link>https://steampunk.si/spotter/glossary/terraform/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform/</guid><description>&lt;p&gt;&lt;strong&gt;Terraform&lt;/strong&gt; is an infrastructure as code tool created by HashiCorp that provisions and manages cloud and on-premises resources from declarative configuration files. You describe the infrastructure you want in HashiCorp Configuration Language (HCL), and Terraform calculates and applies the changes needed to reach that state.&lt;/p&gt;
&lt;p&gt;Teams use Terraform to create and change cloud resources such as networks, virtual machines, databases, Kubernetes clusters, DNS records and IAM roles. It works across AWS, Azure, Google Cloud and hundreds of other platforms through providers.&lt;/p&gt;</description></item><item><title>Terraform linting (TFLint)</title><link>https://steampunk.si/spotter/glossary/terraform-linting-tflint/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-linting-tflint/</guid><description>&lt;p&gt;&lt;strong&gt;TFLint&lt;/strong&gt; is an open source linter for Terraform. It checks configuration for errors that &lt;code&gt;terraform validate&lt;/code&gt; misses, such as invalid instance types for a cloud provider, deprecated syntax, unused declarations and naming convention violations. Provider-specific rule sets extend it for AWS, Azure and Google Cloud.&lt;/p&gt;
&lt;p&gt;Linting is the first layer of Terraform quality. Teams usually run &lt;code&gt;terraform fmt&lt;/code&gt;, &lt;code&gt;terraform validate&lt;/code&gt; and TFLint together in pre-commit hooks and CI/CD.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Linting vs policy enforcement.&lt;/strong&gt; A linter checks whether code is well-formed and follows conventions. Policy enforcement checks whether code meets organizational rules, such as approved providers, required encryption or compliance controls, and blocks it if not. Most teams need both. Steampunk Spotter adds governance for Terraform plans: compatibility, breaking changes and custom policies.&lt;/p&gt;</description></item><item><title>Terraform module</title><link>https://steampunk.si/spotter/glossary/terraform-module/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-module/</guid><description>&lt;p&gt;A &lt;strong&gt;Terraform module&lt;/strong&gt; is a reusable package of Terraform configuration that groups related resources, such as a VPC with its subnets and route tables. Modules take input variables and return outputs, so teams can create the same infrastructure pattern many times without copying code.&lt;/p&gt;
&lt;p&gt;Every Terraform configuration is a module: the root module is the directory you run Terraform in. Child modules are called with a &lt;code&gt;module&lt;/code&gt; block and can come from a local path, a Git repository or the Terraform Registry. Popular community modules include the &lt;code&gt;terraform-aws-modules&lt;/code&gt; collection.&lt;/p&gt;</description></item><item><title>Terraform plan</title><link>https://steampunk.si/spotter/glossary/terraform-plan/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-plan/</guid><description>&lt;p&gt;A &lt;strong&gt;Terraform plan&lt;/strong&gt; is a preview of the changes Terraform will make to reach the state described in your configuration. Running &lt;code&gt;terraform plan&lt;/code&gt; compares the configuration with the state file and real infrastructure, then lists every resource to be created, updated, replaced or destroyed. Nothing changes until you run &lt;code&gt;terraform apply&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The plan is Terraform&amp;rsquo;s dry run, and the most important review point in the workflow. A single changed argument can force a resource to be destroyed and recreated, and the plan is where that becomes visible.&lt;/p&gt;</description></item><item><title>Terraform provider</title><link>https://steampunk.si/spotter/glossary/terraform-provider/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-provider/</guid><description>&lt;p&gt;A &lt;strong&gt;Terraform provider&lt;/strong&gt; is a plugin that lets Terraform manage resources on a specific platform, such as AWS, Azure, Google Cloud, Kubernetes or PostgreSQL. Each provider translates Terraform configuration into that platform&amp;rsquo;s API calls and defines the resource types and data sources you can use.&lt;/p&gt;
&lt;p&gt;Providers are published in the Terraform Registry and declared in a &lt;code&gt;required_providers&lt;/code&gt; block with a source and version constraint. &lt;code&gt;terraform init&lt;/code&gt; downloads them and records exact versions in the &lt;code&gt;.terraform.lock.hcl&lt;/code&gt; file.&lt;/p&gt;</description></item><item><title>Terraform security</title><link>https://steampunk.si/spotter/glossary/terraform-security/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-security/</guid><description>&lt;p&gt;&lt;strong&gt;Terraform security&lt;/strong&gt; is the practice of making sure Terraform code, state and workflows don&amp;rsquo;t create insecure infrastructure or expose credentials. It covers misconfigured resources, secrets in code or state, unpinned providers and modules, and who can run &lt;code&gt;terraform apply&lt;/code&gt; against production.&lt;/p&gt;
&lt;h2 id="terraform-security-best-practices"&gt;Terraform security best practices&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Pin provider and module versions and review upgrades.&lt;/li&gt;
&lt;li&gt;Store state remotely with encryption, locking and restricted access.&lt;/li&gt;
&lt;li&gt;Never hardcode credentials; use environment variables or a secrets manager.&lt;/li&gt;
&lt;li&gt;Restrict security group rules, and avoid 0.0.0.0/0 on admin ports.&lt;/li&gt;
&lt;li&gt;Enforce encryption, logging and tagging with policy as code.&lt;/li&gt;
&lt;li&gt;Check every plan in CI/CD before apply, and require review for production.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Steampunk Spotter verifies Terraform plans before execution, checking provider compatibility, breaking changes, supply chain risk and custom policies.&lt;/p&gt;</description></item><item><title>Terraform state file</title><link>https://steampunk.si/spotter/glossary/terraform-state-file/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-state-file/</guid><description>&lt;p&gt;The &lt;strong&gt;Terraform state file&lt;/strong&gt; (&lt;code&gt;terraform.tfstate&lt;/code&gt;) is a JSON record that maps the resources in your configuration to the real objects Terraform manages. Terraform uses it to work out what has changed, what to create and what to destroy on the next plan.&lt;/p&gt;
&lt;p&gt;Teams store state in a remote backend, such as Amazon S3, Azure Storage, Google Cloud Storage or HCP Terraform, with locking so two runs can&amp;rsquo;t change it at once. Local state files don&amp;rsquo;t work for teams.&lt;/p&gt;</description></item><item><title>Terraform variables file (.tfvars)</title><link>https://steampunk.si/spotter/glossary/terraform-tfvars/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/glossary/terraform-tfvars/</guid><description>&lt;p&gt;A &lt;strong&gt;.tfvars file&lt;/strong&gt; sets values for the input variables declared in a Terraform configuration. It separates configuration from environment-specific values, so the same code can deploy to development, staging and production with different settings, such as instance sizes or region names.&lt;/p&gt;
&lt;p&gt;Terraform loads &lt;code&gt;terraform.tfvars&lt;/code&gt; and any &lt;code&gt;*.auto.tfvars&lt;/code&gt; files automatically. Other files are passed with &lt;code&gt;-var-file=prod.tfvars&lt;/code&gt;. Variables themselves are declared in a &lt;code&gt;variables.tf&lt;/code&gt; file with a type, description and optional default.&lt;/p&gt;</description></item><item><title>The value of high-quality Ansible Collections | XLAB Steampunk</title><link>https://steampunk.si/webinars-training/value-high-quality-ansible-collections/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/webinars-training/value-high-quality-ansible-collections/</guid><description>&lt;p&gt;Automation plays an increasingly important role in improving the utilization of existing resources and adopting new technology among users.
Ansible Collections form a bridge between Ansible and the automated product.
Because of their central role, the quality of Ansible Collections significantly impacts user experience and the reliability of automated processes.&lt;/p&gt;
&lt;p&gt;By the end of this webinar, you’ll understand the value of high-quality Ansible Collections and the core principles of building and
maintaining user-focused Ansible content. ISVs will see how high-quality Ansible Collections benefit their products and their users,
Ansible Collection developers will learn the basics of designing high-quality plugins and modules and why quality matters when it comes to user experience,
and Ansible users will find out what to expect from an Ansible Collection.&lt;/p&gt;</description></item><item><title>Upgrade Playbooks</title><link>https://steampunk.si/spotter/getting-started/upgrade-playbooks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/getting-started/upgrade-playbooks/</guid><description>&lt;p&gt;You’ll find Spotter to become your best friend when dealing with Ansible upgrades. It checks if your playbooks are compatible with the latest Ansible version, advises you on what to do to avoid breaking them and helps you speed up the upgrade itself using the rewrite function and other features. To learn more about how to use Spotter to speed up and simplify Ansible upgrades, 
&lt;a target="_blank" rel="noopener noreferrer" href="https://steampunk.si/webinars-training/step-by-step-analysis-of-ansible-upgrade/"&gt;watch this webinar&lt;/a&gt;
 or this 
&lt;a target="_blank" rel="noopener noreferrer" href="https://www.youtube.com/watch?v=L6zzbDtymj8"&gt;short demo&lt;/a&gt;
.&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description></item><item><title>What AI Gets Right and Wrong in Your Ansible and Terraform Automation</title><link>https://steampunk.si/spotter/webinars-training/what-ai-gets-right-and-wrong-in-ansible-terraform-automation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://steampunk.si/spotter/webinars-training/what-ai-gets-right-and-wrong-in-ansible-terraform-automation/</guid><description>&lt;p&gt;In this session, we will show you the results of AI generated and modified automation through three real-world use cases. First, we look at an Ansible Playbook and Terraform configuration generated with AI from scratch. Then we examine what happened when the team used AI to upgrade and secure an existing set of Playbooks. In all three cases, we break down the results: what AI got right, what it missed, and where it confidently got things wrong – including issues that could easily make it into production.&lt;/p&gt;</description></item></channel></rss>