Create automated way of issuing Replicated licenses #8717
Labels
meta: stale
This issue/PR is stale and will be closed soon
team: delivery
Issue belongs to the self-hosted team
In order to issue a Replicated license, you must use the Replicated CLI to generate the license.
Community license
Assuming that the Replicated feature request to allow for a license to be changed via the KOTS UI is accepted, we can issue a single community license to allow for anonymous use of Replicated.
stable
,beta
andunstable
- there is an appetite in the community to track the bleeding-edge releases.Professional license
stable
only. Other channels can be added later if necessary.This license generator makes sense to be done as a serverless component. Replicated does not offer access to their API via the web, but does so via their CLI tool. As this would be our first (to my knowledge) serverless component, this would require some architectural thought.
How the license would be delivered would require some thought as well - downloading or emailing are the two basic options. Again, this would need doing from the Replicated CLI.
One question that needs answering is how to add values for the license fields (domain, levelId and seats) to the license via the CLI as it's not documented. I have raised this with Replicated.
The text was updated successfully, but these errors were encountered: