Vinicius D. Cerutti
Vinicius D. Cerutti
## Motivation We at Quansight have integrated Prefect within QHub to allow for easy workflow management. Currently we are maintaining a helm chart within QHub for a [prefect agent only...
## Changes introduced in this PR: - Update `filesystem` and `default` environment names to `nebari-git` and `global` respectfully related to #1349 ## Types of changes What types of changes does...
### Feature description The current Welcome message is outdated and sends the user to an invalid repository. - Update the `theme.jupyterhub.welcome` to a proper welcoming message. [ref.](https://github.com/Quansight/qhub/blob/ee41b5eb41632b23adc6b1d1a62e67abd6937bac/qhub/initialize.py#L327) ### Value and/or...
### Feature description The Terraform Provision and Terraform Apply steps in the `qhub deploy` could be executed as a `dry run,` just like running the [terraform plan](https://www.terraform.io/docs/commands/plan.html) command. The dry...
The environment names for `filesystem` and `default` leads to some misconception about what these environments are used for and how they can be managed. We need to create some documentation...
- This is a meta issue to track work for 0.4.2 Milestone
We've been recently upgrading some outdated Kubernetes API calls from the current providers and resources, but I noticed the following message in all of our current deployments on GCP: >...
### OS system and architecture in which you are running QHub linux ### Expected behavior QHub should by default be able to spawn a user server based on qhub configmaps...
Recently we ended up having some issues with outdated helm charts and/or missing charts that impacted our deployment greatly. I suggest we add some kind of tracking system to have...
We need to re-enable this tooling cited in the [docs](https://docs.qhub.dev/en/stable/source/installation/configuration.html?highlight=qhub_#omitting-sensitive-values). Which was originally created to solve #13.