Import projects via config file

[applejag]

Declaring what to import already from a config file / k8s Secret.

Use case: Spin up new environments that is pre-populated

This is a feature request from a user who had to reset their postgres because KubeDB f*cked up. But the "spin up pre-populated environment of Wharf" is a promising feature.

This should get an RFC!

Concerns:

• There will be secrets in these configs.

• This would involve the API having to speak with the providers. We have to be careful here not to introduce a circular dependency chain as the providers currently depend on the API. Or the providers read the config instead

• Either we watch for updates in the configfile, allowing hot reloading, or we only import on boot. Config could have settings such as:

  importOnStartup: true
  importOnConfigChange: true

[applejag]

Maybe a new "Import from config" operation in the frontend via new API endpoint?

Trigger it with .wharf-ci.yml?

Pros of auto importing:

• Can be deployed without further actions

Cons of auto importing:

• More error prone. We have to deal with project collisions and previously deleted projects