<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure as Code on Romano Roth</title><link>https://romanoroth.com/en/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure as Code on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Sun, 09 Jan 2022 20:17:55 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>What is Respond? | SAFe DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-respond-safe-devops-health-radar/</link><pubDate>Sun, 09 Jan 2022 20:17:55 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-respond-safe-devops-health-radar/</guid><description>&lt;p>How do you proactively detect and fix production issues before they cause a business disruption? Respond is the SAFe DevOps Health Radar activity that answers exactly this question. In this video, I walk through what Respond involves and why it is essential for maintaining a stable production environment.&lt;/p></description></item><item><title>What is Deploy? | SAFe DevOps Health Radar</title><link>https://romanoroth.com/en/blogs/what-is-deploy-safe-devops-health-radar/</link><pubDate>Sun, 21 Nov 2021 20:46:47 +0000</pubDate><guid>https://romanoroth.com/en/blogs/what-is-deploy-safe-devops-health-radar/</guid><description>&lt;p>Deploy is a critical step in the SAFe for DevOps Health Radar. After we have built a deployable package and tested it in a staging environment, we now want to continuously deploy our changes into the production environment. The goal is to deploy with high frequency and low risk. In this video, I explain how we achieve this and what practices enable continuous deployment.&lt;/p></description></item></channel></rss>