The Path to DevOps Self-Service: A Five-Part Series

Summary of a five-part series to unlock the potential of DevOps self-service

Diagram adapted by author from stock image in Lucidchart

Thank you for journeying along with me on this path to DevOps self-service. We focused on different aspects of DevOps self-service in my last five stories. In this story, we are going to take a visual tour, guided by the pipeline architectural diagram, string these five parts into one series, and review the many facets of DevOps self-service.

This five-part series is by no means comprehensive, there is so much more to explore on the path to DevOps self-service. If you come across any area related to DevOps self-service that’s not covered in this series, do leave me a comment.

Now let’s review this five-part series.

Part 1: DevOps Self-Service Pipeline Architecture and Its 3–2–1 Rule

Before diving into the details, it’s important to get an overall understanding of what our self-service pipeline architecture looks like, the key ingredients, and its unique 3–2–1 rule. We focused on the overall DevOps self-service pipeline architecture and its 3–2–1 rule in Part 1. To recap this 3–2–1 rule:

• 3 types of source code: Terraform code, project source code, and GitHub…