As a new member of the API Platform team,
I want to understand how our software starts from local development to production
so that I'm aware of how my changes get promoted through our development lifecycle
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | VirginiaPoundstone | T284325 Example Node Prototype API | |||
| Resolved | • sdkim | T284755 Document our Path to Production |
Wikimedia production services shouldn't be run in Toolforge/cloudVPS, its meant as a non-prod environment for quick iteration. I would suggest we echo this in our guidelines:
Develop and deploy non-prod/iterative api on cloud services
Once ready for production (releng agreed there was ambiguity with what that actually means) deploy to k8s
Security team chimed in to say that there already exists production-ish services on cloud services. but that they really would prefer that not to be a thing anymore (security wise)