Skip to content

A greenfield IaC platform that became the company standard

Role: Architect and largest contributor2023 – nowPositive Technologies

Internal details are anonymised under NDA. Diagrams are redrawn and the numbers rounded.

  1. Git repository
  2. CI component
  3. Execution environment
  4. Terraform / Ansible
  5. AWS · OpenStack · VMware
Redrawn, simplified flow

problem

Infrastructure was changed through manual operations. Every change depended on the person making it, and nothing guaranteed that two environments were built the same way. Credentials were hard-coded in the automation.

what I did

I designed and built an infrastructure-as-code platform from scratch, and shipped a production-ready version within my probation period.

  • One way to run automation. I built a catalog of reusable GitLab CI components and standard execution environments for Terraform, OpenTofu and Ansible, so every repository builds the same way and builds are reproducible.
  • No hard-coded credentials. HashiCorp Vault holds secrets centrally and injects them into pipelines at run time.
  • Versioned building blocks. A private Terraform registry governs module versions. Ansible roles and collections configure hosts idempotently across AWS, OpenStack and VMware.
  • Faster pipelines. A shared CI base image cut build times from 15–20 minutes to 7–10.

The platform became the organisation’s standard for service delivery. I remain its largest contributor and own it end to end.

Outcome

  • 600repositories in the estate
  • 100+Ansible roles
  • ~20reusable CI components
  • 15–20 → 7–10 minCI build time with a shared base image

Stack

TerraformOpenTofuAnsibleGitLab CIVaultDockerAWSOpenStackVMware