gitpod-io / gitpod-io/gitpod

[licensing] Replicated `dev` license type appears as an invalid license

Open
#10,706 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: dashboard meta: never-stale team: delivery team: webapp type: bug
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Bug description

Our replicated licenses have license types of (community, trial, prod, and dev); these values are also defined within Replicated. However issuing and using a dev license causes the dashboard License page to indicate that an inactive or unknown license is in use. While a minor issue it's pretty confusing, and complicates testing I'm doing around invalid licenses.

It looks like this is due to the dashbaord License page only supporting [community, trial, and prod license types](. The dev license type is not handled and it looks like we fall through to an inactive license type.)

Steps to reproduce
  1. Create a Replicated license with type prod.
  2. Create a new self hosted Gitpod instance and confirm that the prod license is displayed as expected.
    Screen Shot 2022-06-16 at 1 14 48 PM
  3. Convert the Replicated license to type dev, sync the license in the KOTS admin page, and redeploy Gitpod.
  4. Visit the Gitpod license page and get an invalid or unknown license.
    Screen Shot 2022-06-16 at 1 20 31 PM
Workspace affected

No response

Expected behavior

The Admin/License page should indicate that the active license is a development license.

Example repository

No response

Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the dashboard License page and trace how replicated license types are interpreted, focusing on the handling of community, trial, prod, and dev. Reproduce the issue by syncing a Replicated license converted to dev, then verify that the Admin/License page identifies it as an active development license rather than invalid or unknown.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.