-
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
Remove old CLI + cleanup #1519
Remove old CLI + cleanup #1519
Conversation
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.
These changes look fine to me, and I don't think they could break any major process. Are we testing the keycloak add user command in the tests bellow? if yes, then I would say that this is ready to go 😄
We are indeed testing adding and listing keycloak users: nebari/.github/workflows/kubernetes_test.yaml Line 127 in c08ee71
Thanks @viniciusdc :) |
@iameskild could you fix the conflict below? after that, this is ready for merge and we will be in place for another RC |
* 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 <taniar.allard@gmail.com> * Update stage 08 folder names * Update nebari/schema.py Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/azure/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/do/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/03-kubernetes-initialize/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/05-kubernetes-keycloak/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/07-kubernetes-services/modules/kubernetes/forwardauth/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update scripts/aws-force-destroy.py Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/constants.py Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * fix flake8 complaint * Update ref to qhub-dask to nebari-dask * Update readme * Change to PYPI_API_TOKEN Co-authored-by: viniciusdc <vinivdc2009@hotmail.com> Co-authored-by: Tania Allard <taniar.allard@gmail.com> Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com> * 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 <dtu.amit@gmail.com> Co-authored-by: Nebari-sensei <116370392+nebari-sensei@users.noreply.github.com> * 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 <51954708+viniciusdc@users.noreply.github.com> * 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 <pavithraes@outlook.com> Co-authored-by: viniciusdc <vinivdc2009@hotmail.com> Co-authored-by: Tania Allard <taniar.allard@gmail.com> Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com> Co-authored-by: Filipe Laíns <filipe.lains@gmail.com> Co-authored-by: Amit Kumar <dtu.amit@gmail.com> Co-authored-by: Nebari-sensei <116370392+nebari-sensei@users.noreply.github.com>
Fixes | Closes | Resolves #
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.