<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Cliff Hults</title><link>https://www.haguest.com/tags/devops/</link><description>Recent content in DevOps on Cliff Hults</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Cliff Hults</copyright><lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.haguest.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing an Automated Artifact Factory: A Case Study in Turning Pipeline Pain Into a Platform Boundary</title><link>https://www.haguest.com/posts/2026-09-20-automated-artifact-factory/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-09-20-automated-artifact-factory/</guid><description>&lt;p>Every team wiring the same three security checks into its own pipeline isn&amp;rsquo;t really a security problem. It&amp;rsquo;s a platform problem wearing a security costume.&lt;/p>
&lt;p>This is the story of how we traced that pattern back to a structural issue, and the design we landed on to fix it: an automated artifact factory that turns signing, vulnerability scanning, and antivirus scanning from something every team bolts onto their own pipeline into something the platform just does for them.&lt;/p></description></item><item><title>When Your Security Tool Goes Down: Surviving an SCA Tool Outage</title><link>https://www.haguest.com/posts/2026-04-12-sca-tool-outage/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-04-12-sca-tool-outage/</guid><description>&lt;p>Security tooling exists to protect your organization. But what happens when the security tool itself becomes the outage?&lt;/p>
&lt;p>That&amp;rsquo;s the situation we found ourselves in when an SCA tool experienced a service disruption that lasted approximately five hours. For us, it wasn&amp;rsquo;t a degraded experience; it was a complete development freeze.&lt;/p></description></item><item><title>Prompt Engineering Isn't Magic — Here's How I Did It in Production</title><link>https://www.haguest.com/posts/2026-04-11-prompt-engineering-in-production/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-04-11-prompt-engineering-in-production/</guid><description>&lt;p>Most prompt engineering content is written by people who have never shipped AI into a real system. This post is different.&lt;/p>
&lt;p>I&amp;rsquo;m a Staff DevOps Engineer. I&amp;rsquo;ve spent time integrating AWS Bedrock into actual production workflows inside a FedRAMP High environment, not demos, not notebooks, not prototypes. Real systems with real constraints and real failure modes.&lt;/p>
&lt;p>Here&amp;rsquo;s what I learned.&lt;/p></description></item><item><title>Supply Chain Attacks Start in Your Build Cache</title><link>https://www.haguest.com/posts/2026-04-11-axios-supply-chain/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2026-04-11-axios-supply-chain/</guid><description>&lt;p>On March 25, 2025, a malicious version of the axios npm package (version 1.14.1) was published to the npm registry. It contained a bundled dependency called &lt;code>plain-crypto-js@4.2.0&lt;/code>, which was later confirmed to be malicious. The package was identified and removed from the npm registry within roughly three hours.&lt;/p>
&lt;p>For most organizations, three hours sounds manageable. For us, it wasn&amp;rsquo;t that simple.&lt;/p></description></item><item><title>Building Images for GCP</title><link>https://www.haguest.com/posts/2019-10-20-gcp-image-build/</link><pubDate>Sun, 20 Oct 2019 04:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2019-10-20-gcp-image-build/</guid><description>&lt;p>In my last post, I opened with the fact that my company has decided to dive into the world of GCP to get ahead of most of the market in our space. With a few of us being tasked for this initive, I decided to take it upon myself to look into &lt;a href="https://packer.io" target="_blank" rel="noreferrer">Packer&lt;/a>. The goal would be to roll our homebrewed software/OS image into an automated build process to make images in GCP (or AWS, vSphere, etc.).&lt;/p></description></item><item><title>Vault Journey</title><link>https://www.haguest.com/posts/2019-09-11-vault-journey/</link><pubDate>Wed, 11 Sep 2019 04:00:00 +0000</pubDate><guid>https://www.haguest.com/posts/2019-09-11-vault-journey/</guid><description>&lt;p>Being a good SysAdmin requires some sense of laziness. In the spirit of that approach, I&amp;rsquo;ve spent some time looking into Hashicorp&amp;rsquo;s Terraform and Red Hat&amp;rsquo;s Ansible tools in my organization&amp;rsquo;s route to Google Cloud Platform. I wanted a method to create reproducible Compute Engine VMs that would allow us to easily create multiple hosts with minor changes quickly and easily.&lt;/p>
&lt;p>I decided that with the use of Terraform, Vault (also from Hashicorp) would allow me to templatize the configs, as well as, create secrets/passwords that would be randomized, able to be called at will, and even automatically rolled with a configured frequency.&lt;/p></description></item></channel></rss>