Ephemeral Dev Environment Provisioner

The Problem and Why It Mattered

I built an on-demand ephemeral environment provisioner — developers spin up a full, isolated copy of the production stack (GKE namespace, Cloud Run, Cloud SQL clone) from a Slack command or GitHub PR label, and it auto-tears down after a configurable TTL. The relevant technical and business risk is the cost of leaving this workflow, control, or product boundary unclear, manual, insecure, or difficult to operate. The case study focuses on the decisions used to make that risk manageable.

Objectives and Success Criteria

• Deliver the capability described in the project objective using a maintainable technical design.
• Make the main workflow, control boundary, and operational responsibilities explicit.
• Produce reviewable implementation evidence without publishing confidential values or customer data.

Requirements and Constraints

The delivery design had to be repeatable across environments, minimise direct production access, and retain enough evidence to investigate and roll back change safely.

My Role and Ownership

I owned the technical design and implementation described in this portfolio record, including the technology choices, core system boundaries, and the documentation of the resulting approach. Related organisational decisions, vendor operations, and formal certification decisions remain outside the scope of this technical case study unless stated explicitly.

Solution Overview

The solution is built around Terraform, Cloud Build, GKE. Its implementation is organised as the components below so that the architecture, control points, and operating model can be evaluated separately rather than treated as a list of tools.

Architecture and System Design

The public architecture description follows the path from the initiating user, workload, or operator action through the relevant devops components. Access boundaries, data or state handling, and operational controls are described at a safe level; secrets, private addresses, and client-sensitive implementation details are intentionally omitted.

Technology Decisions and Trade-Offs

I selected Terraform, Cloud Build, GKE because they support the project objective and make the critical engineering boundaries explicit. The trade-off is operational and platform complexity: the design depends on documented configuration, controlled access, and ongoing review rather than assuming that a managed service or framework removes engineering responsibility.

Implementation Walkthrough

The following implementation notes describe the components that matter most to the project outcome. They are intentionally focused on technical decisions and operating behaviour instead of reproducing entire source files or sensitive configuration.

Implementation: Provisioner Architecture

A Slack slash command (/env create feature-branch) or a GitHub PR label (env: create) triggers a Cloud Build pipeline. The pipeline runs a parameterised Terraform module creating: a dedicated GKE namespace, Cloud Run instances for each microservice (with the PR's Docker image), a Cloud SQL clone of the latest production backup, a Firestore emulator, and a unique subdomain (feature-123.dev.intellidoc.app).

Implementation: Resource Isolation & TTL

Each environment runs with its own service account (no production access), VPC firewall rules, and Cloud Storage buckets. Default TTL: 24h for branch environments, 72h for PR environments. Cloud Scheduler checks hourly for expired envs and triggers Terraform destroy. PR merge/close immediately triggers teardown via webhook.

Implementation: Developer Experience & Cost Guard

When ready (8-12 minutes), a Slack message posts the env URL, build logs, and teardown time. /env list shows all active environments with costs and expiry. /env extend extends TTL. A BigQuery query runs hourly summing estimated cost; alerts if total exceeds $50/day. Idle envs (>4h) flagged for early teardown.

Challenges, Failures and Corrections

This portfolio record does not invent deployment failures, client incidents, or corrective actions that are not supported by the published project evidence. Where operational details are confidential or were not captured for public release, the case study documents the design boundary and lesson instead of presenting an unsupported narrative.

Security, Compliance and Risk

The implementation is described with least privilege, traceability, controlled configuration, and evidence boundaries in mind. Where the project supports a regulated environment, these are technical safeguards and audit-readiness contributions, not a claim that an application or product is independently certified.

Testing, Validation and Evidence

The evidence published for this project is the documented implementation, its stated architecture and controls, and the portfolio record. The published record documents the implemented architecture, the core controls, and the technology choices that can be reviewed without exposing confidential operational data. Claims are limited to the implementation details and outcomes documented in this case study.

Results and Evidence

The published record documents the implemented architecture, the core controls, and the technology choices that can be reviewed without exposing confidential operational data.

What I Learned

This project reinforced that devops work is not a technology checklist. The durable value comes from making boundaries, trade-offs, ownership, and evidence clear enough for another engineer or stakeholder to review and operate the system responsibly.

What I Would Improve Next

• Expand automated validation around the most important workflow and control boundaries.
• Add or deepen operational evidence, such as dashboards, test artefacts, or an architecture diagram where it is safe to publish one.
• Review the design against the next expected scale, reliability, and governance requirement before extending the system.

Final Takeaway

This devops and platform engineering case study addresses a defined technical problem through Terraform, Cloud Build, GKE. It demonstrates my ability to turn requirements into an explainable design, implement the important controls, and document outcomes and limitations without overstating what the evidence proves.