dbaas-controller actions from projects

[tnelson-doghouse]

Idea: Projects can hit up the dbaas controller to provision new databases on the fly (ie. for tenants)

[shreddedbacon]

Not sure what your idea is here. Can you expand on it a bit more with a use case?

[tnelson-doghouse]

Use case (with extra spitballing):

• Project environment wants to create a new tenant.
• Tenants each live in their own database
• Environment calls an API on the dbaas-controller (or something that proxies to it -- whatever), specifying a tenant and maybe a slug
• DBaaS operator:
  • Creates new database (with the name eg. project-environment-tenant-slug)
  • Creates new database user
  • Stores the username/password somewhere so that they can be loaded into the environment on the next deploy
  • Returns the new database/username/password to the calling environment
• Project environment now uses the database. Voila, there's a new tenant with no redeploy.

The actual process probably needs to change, but I thought this might give the picture.

HTH,

[shreddedbacon]

This is already the core function of the dbaas-controller, it handles creating credentials and connection details for services.

Adding services outside of what exists in the docker-compose.yml file of an environment is not something that Lagoon even supports, and is a pretty significant deviation from the basic idea behind Lagoon. That being that what is defined in docker-compose is what gets deployed.

In any case, a deploy of some sort would need to take place for the pods and other things to get the credentials and service endpoints loaded into the environment. So you're still best off just adding your tenants to your docker-compose.yml file and redeploying.