Skip to content

Deprecate gitpod.yml config stored in the DB #9102

Closed
@easyCZ

Description

@easyCZ

Is your feature request related to a problem? Please describe

There are currently 3 ways that a gitpod.yml can be injected into a workspace:

  • Repository contains a .gitpod.yml file
  • Project has been configured with a Database level gitpod.yml. This config is stored on the Project level, and not in the repository
  • Using definitely-gp, scheduled for deprecation in Epic: Deprecate definitely-gp  #8473

The existing solution results in inconsistent handling of gitpod.yml definitions. The intention of this change is drive towards a single workflow for defining gitpod.yml specification.

This Issue desribes the what and acts as a tracking issue, the how is yet to be determined.

CC @jldec for filling more details on why and the product take on this.

Metadata

Metadata

Assignees

Labels

team: webappIssue belongs to the WebApp team

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions