Enhancement of Playground

[kentakozuka]

Objective

Community Growth

Tactics

Enhancement of Playground

• User can create project (via form request).
• User can be admin of the project.
• User can do anything inside the project.

Why we do this?

Lower the bar to play with PipeCD

• User does not have to deploy the control plane.
  • Currently, if potential users wants to check the behaviour of ECS application, they have to deploy the control plane and expose its API to piped. (Deploying the control plane is not as easy as the quickstart)
• User can try all features of PipeCD.

How to provide it?

• Multi-tenancy
  • 1 control plane, multi-users
• 1 user; 1 project

MVP

We don’t know how many people want to try.
So, let’s start with minimum setup.

Use playground

• Add projects to the playground

User request flow

• Get requests on Google Form
  • We can confirm the email is owned by the requester.
  • We can limit only one request per Google account.
• Create project manually.
• Send static admin’s username and password via email.

Risks

Security

• Too many requests

Cost

• GCP Budget should be reconsidered.
• Set resource limit

Object name	Todo	Type	Size	Limit
Project	NOT	datastore
API key	YES	datastore	300B	max 5
Application	YES	datastore		max 5
Deployment	YES	datastore		max 1 per 1min
Deployment chain	YES	datastore		max 3
Command	YES	datastore
Event	YES	datastore
Piped	YES	datastore		max 3
App manifest	YES	filestore

[kentakozuka]

todo: investigate MySQL trigger to satisfy the needs.