Incorporate Gitpod licence into Replicated licence

[mrsimonemms]

Replicated requires users to have a licence to get started. Investigate the possibility of configuring this licence so that it incorporates the Gitpod licence.

When speaking to Todd, I got the impression that you can attach custom data to the Replicated licence - if that is accurate, perhaps we could attach our licence as a custom field and then build a secret from that and inject into the config.

If that's not possible, we will have to investigate ways of altering the Gitpod licence so it is compatible with the Replicated licence.

The licence can be retrieved from the config using it's context function.

[mrsimonemms]

Yes, custom licence fields are possible. At it's simplest form, we could just have a field "Gitpod licence" and then extract that to a secret and update the config

[corneliusludmann]

The licence can be retrieved from the config using it's context function.

update the config

I was under the impression we needed to be able to check the license at run time. I'll have to think about it again. However:

There is also a License API that can be accessed from within Gitpod at runtime. With this, we can implement an additional LicenseEvaluator and LicenseKeySource that talks with the Replicated API instead.

[metcalfc]

One of the goals was to automate the licenses generation and auditing. We can do that through the replicated licenses. Lets replace our licensing with theirs. We can give internal users a license API that we can implement and mock out. So that SaaS doesn't have to think about it.