-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name change QHub --> Nebari #1508
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Thanks, @iameskild !!! |
💰 Infracost estimate: monthly cost will not change
9 projects have no cost estimate changes. Infracost output
This comment will be updated when the cost estimate changes. Is this comment useful? Yes, No, Other |
@iameskild, thanks for fixing the upgrade tests! 😄 @trallard for now, we will keep the mentions of qhub in there, as it's heavily used by the I was working on this to ship together with the migration, but there are some bits that will require more attention |
Also, we need to start testing for Python |
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
…riables.tf Co-authored-by: Tania Allard <[email protected]>
…riables.tf Co-authored-by: Tania Allard <[email protected]>
…es/forwardauth/variables.tf Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Co-authored-by: Vinicius D. Cerutti <[email protected]>
Co-authored-by: Tania Allard <[email protected]>
Thanks for the review @trallard!! As @viniciusdc pointed out somewhere, the references to |
# DNS prefix specified when creating the managed cluster. Changing this forces a new resource to be created. | ||
dns_prefix = "Qhub" # required | ||
dns_prefix = "Nebari" # required | ||
|
||
# Azure requires that a new, non-existent Resource Group is used, as otherwise the provisioning of the Kubernetes Service will fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just flagging this as important information for the migration notes
@@ -1,4 +1,4 @@ | |||
resource "random_password" "keycloak-qhub-bot-password" { | |||
resource "random_password" "keycloak-nebari-bot-password" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uhm... this will change Keycloak admin-level password, not user interactable but its good to flag
@@ -1,4 +1,4 @@ | |||
from qhub_jupyterhub_theme import theme_extra_handlers, theme_template_paths | |||
from nebari_jupyterhub_theme import theme_extra_handlers, theme_template_paths |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was this released?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, we need to discuss about upgrade and the theming changes
* Switch to CalVer (#1501) * Run CI on branchs release/** * Update pyproject.toml to use calver * Update on branch * Update theme welcome messages to use Nebari (#1503) * update welcome messge * remove qhub specifics from theme * Name change QHub --> Nebari (#1508) * Name change: .github * Name change: qhub/ * Name change: tests/ * Name change: tests_deployment/ * Name change: tests_e2e/ * Name change: / * Rename folder * Rename releases * Remove qhub/ * Run pre-commit * Revert docs links * Fix infracost artifact names * Update upgrade command + test * Updates based on review * Update step output format * Fix: Update step output format * Update nebari/provider/cicd/common.py Co-authored-by: Tania Allard <[email protected]> * Update stage 08 folder names * Update nebari/schema.py Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/02-infrastructure/azure/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/02-infrastructure/do/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/03-kubernetes-initialize/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/05-kubernetes-keycloak/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update nebari/template/stages/07-kubernetes-services/modules/kubernetes/forwardauth/variables.tf Co-authored-by: Tania Allard <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * Update scripts/aws-force-destroy.py Co-authored-by: Tania Allard <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * Update nebari/constants.py Co-authored-by: Vinicius D. Cerutti <[email protected]> * Update setup.cfg Co-authored-by: Tania Allard <[email protected]> * fix flake8 complaint * Update ref to qhub-dask to nebari-dask * Update readme * Change to PYPI_API_TOKEN Co-authored-by: viniciusdc <[email protected]> Co-authored-by: Tania Allard <[email protected]> Co-authored-by: Vinicius D. Cerutti <[email protected]> * qhub/initialize: lazy load attributes that require remote information (#1509) * qhub/initialize: lazy load attributes that require remote information * Fix broken configuration * fix renaming * fix header text * Update nebari/initialize.py * Update nebari/initialize.py * Blackify Co-authored-by: Amit Kumar <[email protected]> Co-authored-by: Nebari-sensei <[email protected]> * Update README logo (#1514) * Add fix, enhancements and pytests for CLI (#1498) * Add fix, enhancements and pytests for CLI * No zero-padded month for CalVer release branches * Update cli test * Simplify test.yaml * Remove old CLI + cleanup (#1519) * Remove old cli * Update theme * Remove shim * display_version: True * Update `skip_remote_state_provision` default value (#1521) * Add release notes for 2022.10.1 (#1523) * Add release notes for 2022.10.1 * Wording * Update README.md with new docs links * Update README.md with new docs links Co-authored-by: Vinicius D. Cerutti <[email protected]> * Remove leading `v` for release action (#1526) * Remove leading v for release tags * Add note to release checklist * Merge release branch into main Co-authored-by: Pavithra Eswaramoorthy <[email protected]> Co-authored-by: viniciusdc <[email protected]> Co-authored-by: Tania Allard <[email protected]> Co-authored-by: Vinicius D. Cerutti <[email protected]> Co-authored-by: Filipe Laíns <[email protected]> Co-authored-by: Amit Kumar <[email protected]> Co-authored-by: Nebari-sensei <[email protected]>
Fixes | Closes | Resolves #
Closes #1508
Changes introduced in this PR:
Types of changes
What types of changes does your PR introduce?
Put an
x
in the boxes that applyTesting
Requires testing
In case you checked yes, did you write tests?
Documentation
Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?
Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.