* [server] Introduce ReadinessController and probe at /ready
Tool: gitpod/catfood.gitpod.cloud
* [server] Move /live and /ready endpoints to a separate express app and port
Tool: gitpod/catfood.gitpod.cloud
* [memory-bank] task-related learnings
Tool: gitpod/catfood.gitpod.cloud
* [server] Introduce `server_readiness_probe` feature flag so we can disable the ReadinessProbe if required
Tool: gitpod/catfood.gitpod.cloud
* docs: formalize Product Requirements Document workflow
- Add PRD workflow to systemPatterns.md as a standardized development process
- Update .clinerules with instructions to follow the PRD workflow
- Update activeContext.md and progress.md to reference the new workflow
This formalizes the process we used for implementing the server readiness probe feature.
Tool: gitpod/catfood.gitpod.cloud
* [server] ReadinessProbe: add redis as dependency
Tool: gitpod/catfood.gitpod.cloud
* review comments
Tool: gitpod/catfood.gitpod.cloud
* [dev] Remove outdated gopls config
Tool: gitpod/catfood.gitpod.cloud
* [server] Fix import
Tool: gitpod/catfood.gitpod.cloud
* Introduce `max_parallel_running_workspaces` for orgs
* Add migration
* Add UI and org settings server changes
* Rough edges
* Number inputs (:trollface:)
* Move LazyOrganizationService to UBP entitlement service to get rid of circ. dep. errs
* Fix tests
* Update components/gitpod-db/src/typeorm/entity/db-team-settings.ts
Co-authored-by: Gero Posmyk-Leinemann <gero@gitpod.io>
* Rename `isPaidPlan` to `isPaidOrDedicated` and get rid of `update_max_parallel_running_workspaces`
* Update components/server/src/workspace/workspace-service.ts
Co-authored-by: Gero Posmyk-Leinemann <gero@gitpod.io>
* Deduplicate instance counting logic
---------
Co-authored-by: Gero Posmyk-Leinemann <gero@gitpod.io>
* [image-builder-mk3] improve traces and logging
* Add ws-manager-bridge to VS Code workspace
* Setting up gpctl imagebuilds to help with testing
* Fix merge miss
Fixes https://github.com/gitpod-io/gitpod/issues/10766
This PR adds a new `experimental.telemetry.data.platform` config option
that is then passed to `GITPOD_INSTALLATION_PLATFORM` env variable, which
is then transmitted by the `gitpod-telemetry` job as the `platform`
property into our telemetry store. The value of this env variable
is then overrided by each install method.
This env can have the following values:
- `installer` by default as when the installation is done directly
through the installer, We don't have enough information
about the environment.
- [One of the `distribution` values](https://docs.replicated.com/reference/template-functions-static-context#distribution)
when done through `kots`. This would have the distribution in which
Gitpod is being installed, and is dependent on `kots`.
- `local-preview` when the installation is done through the new
preview install method.
As the changes show in the PR, each installation method overrides
the value.
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
