This is useful for testing so we can generate the same rendering
each time and then compare the outputs against a known value. It also
allows users to make their randomisation deterministic
Currently, After `local-preview` is exited There are no
direct concrete steps for users to take.
This PR fixes this by adding a new `Alert` box to the
global dashboard if we notice that they are on a Gitpod
`local-preview` DOMAIN, which is `preview.gitpod-self-hosted.com`
(our own DOMAIN) from now.
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
The name of the object storage bucket to which usage reports are
uploaded needs to be configurable for Gitpod SaaS. GCloud bucket names
are globally unique, so the bucket name must vary between staging and
production.
Currently, The telemetry of `local-preview` is the same as any self-hosted install which
means that these telemetry cronjob is run daily, and also once when the installation is ready.
This information isn't as useful, as the properties aren't that important for a short-lived
installation.
Instead, It would make sense to have telemetry on each event of the `local-preview`
command itself so that we can measure the Installation success rate, Time taken, etc
to improve the overall UX of `local-preview`. This will be more important for us
to understand the usage of `local-preview` itself.
This PR fixes that by attaching a telemetry event to be sent, for each status update
in `local-preview`. For this to work, A anonymous User ID is generated and used
for all status updates.
Event Schema:
```
analytics.track({
userId: userId,
event: "localpreview_status",
properties: {
status: "checking prerequisites" | "starting gitpod" | "gitpod ready"
}
})
```
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
This PR removes the dependency of `cert-manager` and thus
reducing resource usage. This is replaced by the usage of
`mkcert` instead
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
- Use latest workspace instance to set workspace class
- Add more detailed configuration for workspace classes
- Make workspace classes configurable in installer
Currently, There is no way to disable telemetry for `local-preview`
as we run the cronjob manaully during init, when Gitpod is ready.
This fixes that by honouring [`DO_NOT_TRACK` envrionment variable](https://consoledonottrack.com/)
, which when set prevent the script from triggering the cronjob manually.
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
This PR updates the `local-preview` to printout
the Domain of the Gitpod Instance for users to
access.
Signed-off-by: Tarun Pothulapati <tarun@gitpod.io>
