Building a PaaS with Waypoint
summary
Built a small PaaS on top of HashiCorp Waypoint called WayPaaS that auto-generates waypoint.hcl from team templates and enterprise identity, ties repos to projects, and moves artifacts through a git-based build→deploy→release flow. Key commands are waypass init to provision profiles from AAD, waypass create to scaffold per-team defaults for ECS/EKS and ECR, and waypass promote to deploy + run release and open public IP. Current limits: no RBAC, limited testing steps, single-app focus; still PoC with work planned for plugins and multi-service stacks.
AI-written summary · about
chapters (8)
- 0:00Introduction to Waypass
- 2:29Understanding HashiCorp Waypoint
- 5:28Waypoint limitations
- 7:57Bridging the functionality gap
- 10:59Waypass features and setup
- 16:05Deployment and release workflow
- 18:38Future roadmap
- 19:55Summary and Q&A
related talks
28mHCP Waypoint: An internal developer platform made to empower platform teams
19mHashiCorp Waypoint Roadmap - HashiConf Global 2022
28mYour Terraform setup is the foundation for an IDP — extend it to empower developers
53mBuild a self-service internal developer platform
18mSunrise of Platforms as Services (PaaS)
25mMaking the Leap: Transitioning Enterprises to a PaaS Mindset
41mScale infrastructure operations with HCP Terraform self-service workflows
24mFrom Kubernetes to PaaS to Developer Control Planes