How The Cloud Resume Challenge Exposed Real-World DevOps Pitfalls in Azure

From Static HTML to Cloud Infrastructure: My Cloud Resume Challenge Journey

The Cloud Resume Challenge is a project-based test of cloud engineering skills. One IT professional spent two weeks wrestling with Azure Functions runtime versions, CosmosDB partition keys, and GitHub Actions pipeline bugs to deploy a serverless resume app.

Why This Matters

Manual configuration through cloud portals feels simple but collapses under repeated rebuilds. The author found that every architectural decision became fragile when forgotten settings broke deployments; defining infrastructure as code (IaC) via ARM templates eliminated that fragility by ensuring reproducible environments, a practice critical for enterprise reliability.

Key Insights

• “Azure Functions runtime version mismatches”: Node.js version conflicts between GitHub Actions (warning Node 20 deprecated), ARM template (pinned to Node 18), and Azure’s supported list (no Node 24) caused deployment failures. Author had to align all three manually before the Function App worked.
• “CosmosDB Table API visitor counter bug”: First visit crashed because no row existed. Fix required catching the SDK’s 404 error, creating the row with count=1, then incrementing on subsequent visits — a small logic gap that took hours to debug.
• “GitHub Actions pipeline discipline enforced by tests”: Pipeline blocked deployment if Jest tests failed, preventing accidental broken code pushes. Author initially skipped test step dependency and deployed bad code multiple times before wiring it correctly.
• “ARM templates solve manual click fragility”: Deleting resource group and redeploying from scratch in minutes ensured identical environments every time — unlike portal configurations where settings are lost after teardown.

Practical Applications

• “Enterprise IaC adoption -> Use ARM or Terraform templates instead of portal clicks for reproducible deployments”. Pitfall: Skipping IaC leads to unrecoverable manual configurations after each teardown.
• “Serverless visitor counter -> Implement null-check logic in Azure Functions before reading CosmosDB rows”. Pitfall: Assuming row always exists crashes on first visit; handle SDK’s 404 properly.
• “CI/CD automation -> Wire test failure as blocking condition in GitHub Actions workflow”. Pitfall: Deploying without test step dependency allows broken code into production.

References: