GitLab managed Serverless provider
Problem to solve
As an ops engineer, in order to provide serverless capabilities to my fellow developers, I would like to set my preferred serverless provider centrally, and have it used by all the developers without their knowledge.
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
Further details
Devon sets up their GitLab instance so that every serverless project deploys automatically to AWS. She can change this setting under GitLab to start deploying to Knative without harmin any developer.
Proposal
Create a custom Serverless framework provider (the gitlab provider), that actually proxies to a supported serverless provider set as a GitLab setting.
Permissions and Security
Setting up the "real" provider needs project / group / instance admin rights.
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
- Starter plan