CI/CD

Frodo CLI is a powerful command-line tool designed to manage ForgeRock Identity Cloud configurations efficiently. It allows you to export and import journeys, policies, and other configurations, making it an essential part of any CI/CD pipeline for Identity Management. In this post, I’ll walk you through setting up Frodo CLI in GitHub Actions to automate the export and import of journeys. What is Frodo CLI? Frodo CLI is a Node.js-based command-line interface that provides a suite of tools for interacting with ForgeRock Identity Cloud. It supports operations such as exporting and importing journeys, managing policies, and handling various configuration tasks. By integrating Frodo CLI into your CI/CD pipeline, you can automate these processes, ensuring consistency and reducing manual errors. ...

“Did you remember to export the updated Login journey before leaving on Friday?” This Slack message used to haunt our team. Someone would make changes in dev, forget to export, and by Monday we’d be scratching our heads about what changed. Sound familiar? The fix: wire up Frodo CLI with GitHub Actions and never worry about manual exports again. Here’s exactly how we set it up. Why Bother with CI/CD for ForgeRock? Manual Process CI/CD with Frodo Export from admin console git push triggers export Copy JSON files manually Automated version control Import one-by-one Batch import with validation No audit trail Full Git history Human errors Consistent, repeatable CI/CD Pipeline Flow: ...

If you’ve ever spent an afternoon clicking through the ForgeRock admin console to export journeys one by one, or copy-pasted JSON between browser tabs to migrate configurations—you know the pain. I’ve been there, and it’s exactly why Frodo CLI exists. Frodo (ForgeRock DO) is the CLI that ForgeRock should have shipped from day one. It handles PingOne Advanced Identity Cloud, ForgeOps, and classic AM deployments. Once you start using it, you’ll wonder how you ever lived without it. ...

In today’s fast-paced software development landscape, having a reliable and efficient DevOps pipeline is crucial. Building a cross-platform pipeline that works seamlessly on both Mac and Linux environments can be challenging but is highly rewarding. In this guide, we’ll walk through the process of creating a robust DevOps pipeline using Jenkins and Docker, ensuring consistency across Mac and Linux platforms. Visual Overview: graph LR subgraph "CI/CD Pipeline" Code[Code Commit] --> Build[Build] Build --> Test[Test] Test --> Security[Security Scan] Security --> Deploy[Deploy] Deploy --> Monitor[Monitor] end style Code fill:#667eea,color:#fff style Security fill:#f44336,color:#fff style Deploy fill:#4caf50,color:#fff Setting Up Jenkins for Cross-Platform Builds Jenkins is a popular open-source automation server that supports a wide range of plugins and integrations, making it an excellent choice for cross-platform pipelines. To set up Jenkins, follow these steps: ...

In today’s fast-paced software development landscape, integrating security into the DevOps workflow is no longer optional—it’s a necessity. DevSecOps, the union of DevOps and security practices, ensures that security is baked into the software development lifecycle (SDLC) from the very beginning. In this article, I’ll walk you through my DevSecOps pipeline, covering the tools, processes, and best practices that help me deliver secure software from code to production. Visual Overview: ...

I’ve set up 50+ GitHub Actions CI/CD pipelines deploying to Kubernetes. Most teams spend weeks debugging permission issues, image pull errors, and failed deployments. Here’s what actually works in production. Visual Overview: graph LR subgraph "CI/CD Pipeline" Code[Code Commit] --> Build[Build] Build --> Test[Test] Test --> Security[Security Scan] Security --> Deploy[Deploy] Deploy --> Monitor[Monitor] end style Code fill:#667eea,color:#fff style Security fill:#f44336,color:#fff style Deploy fill:#4caf50,color:#fff Why This Matters According to the 2024 State of DevOps Report, teams with mature CI/CD practices deploy 46x more frequently with 7x lower change failure rates. Yet I’ve seen teams abandon Kubernetes deployments after hitting GitHub Actions’ notorious “ImagePullBackOff” errors and RBAC nightmares. ...

papermod—ci-cd–automating-deployment-wit-66a02035.webp alt: “Hugo + PaperMod + CI/CD: Automating Deployment with GitHub Actions” relative: false In the world of modern web development, static site generators like Hugo have become increasingly popular due to their speed, flexibility, and ease of use. Combined with a sleek theme like PaperMod and automated deployment pipelines using GitHub Actions, developers can streamline their workflow and focus on creating content rather than managing infrastructure. In this blog post, we’ll explore how to set up a Hugo site with PaperMod and automate its deployment using CI/CD with GitHub Actions. We’ll also discuss best practices, common pitfalls, and how to optimize your setup for maximum efficiency. ...

Visual Overview: graph LR subgraph "CI/CD Pipeline" Code[Code Commit] --> Build[Build] Build --> Test[Test] Test --> Security[Security Scan] Security --> Deploy[Deploy] Deploy --> Monitor[Monitor] end style Code fill:#667eea,color:#fff style Security fill:#f44336,color:#fff style Deploy fill:#4caf50,color:#fff In the rapidly evolving world of DevOps and cloud computing, ensuring robust security in CI/CD pipelines has become a critical concern. Identity and Access Management (IAM) plays a pivotal role in securing cloud resources, but integrating IAM security testing into CI/CD pipelines can be challenging. This blog explores how to effectively integrate IAM security testing into your CI/CD workflows, ensuring that your applications are secure from the moment code is written to the time it is deployed. ...