chore: remove cognito usage - #290
Merged
Merged
Conversation
|
Contributor
|
We no longer have a cognito auth service (completely replaced by keycloak). Do you mind updating a few notebooks to remove the intro text about using the cognito client to access data outside the hub from the notebooks? If modifying notebooks is a precarious, we can also just open another issue to take care of that as tech debt later. https://github.com/search?q=repo%3ANASA-IMPACT%2Fveda-docs+outside+the+hub+ipynb&type=code |
Contributor
Author
|
I can update them - I was also looking at the binder workflow but it might have wait |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
anayeaye
approved these changes
Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
cognito_client was hard pinning other dependencies, causing the environment upgrades to be unsolvable. It doesn't seem like this is the recommended pattern anymore