-
Notifications
You must be signed in to change notification settings - Fork 497
Enhancements to Secret Management #364
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
58 commits
Select commit
Hold shift + click to select a range
7757f50
use keyring to store credentials
maxjeblick e4a4d52
use keyring migration
maxjeblick dfd5238
update pipfile
maxjeblick 5adb0f2
switch to yaml
maxjeblick f5b9514
try to fix ssh keyring
maxjeblick 419689d
Merge branch 'max/use_keyring_storage' of github.com:h2oai/h2o-llmstu…
maxjeblick 1a6a662
switch to DBUSkeyring
maxjeblick 03d84f2
undo switch to DBUSkeyring
maxjeblick 55c8a88
switch to DBUSkeyring
maxjeblick 26ba4f7
set SecretService in make wave
maxjeblick 75377d0
pop up if secret cannot be saved
maxjeblick 340dfce
pop up if secret cannot be saved
maxjeblick 1b641b6
pop up if secret cannot be saved
maxjeblick e86c4e2
show traceback
maxjeblick 858860a
add factory method for credentials
maxjeblick 449934b
add factory method for credentials
maxjeblick 8023c7a
fix keyring deletion
maxjeblick 24db4a8
fix format
maxjeblick 351e9c6
fix format
maxjeblick a0ecff5
add tests for settings
maxjeblick a1cdb20
refact settings
maxjeblick 4a07912
add readme with updates
maxjeblick a02a1cc
remove make keyring variable
maxjeblick fcdcf0c
fix format
maxjeblick bf4c673
better wording
maxjeblick 95ff87b
better wording
maxjeblick 0c0a0e6
update pipfile
maxjeblick 1630aac
fix pr number
maxjeblick d59f483
Update requirements.txt
maxjeblick cc467f5
Merge branch 'main' into max/use_keyring_storage
maxjeblick 105c209
remove uneeded variables
maxjeblick 29ae38f
Merge branch 'main' into max/use_keyring_storage
maxjeblick 3056be5
Merge branch 'max/use_keyring_storage' of github.com:h2oai/h2o-llmstu…
maxjeblick ebef445
Merge branch 'main' into max/use_keyring_storage
maxjeblick 8efb651
fix merge conflicts
maxjeblick fcda030
refact saveing of user settings
maxjeblick ea1340f
refact saveing of user settings
maxjeblick 33aad0c
add button for no setting error pop up
maxjeblick 6e8a829
Merge branch 'main' into max/use_keyring_storage
maxjeblick 512ad37
Merge branch 'main' into max/use_keyring_storage
maxjeblick e081e3c
first save/load secrets
maxjeblick a95cb5a
more type annotations
maxjeblick 7581249
Merge branch 'main' into max/use_keyring_storage
maxjeblick 037aadc
Merge branch 'main' into max/use_keyring_storage
maxjeblick e965ffc
Merge branch 'max/use_keyring_storage' of github.com:h2oai/h2o-llmstu…
maxjeblick a494812
fix merge conflicts
maxjeblick 97faf73
add keyring dependency
maxjeblick 051d006
Update requirements.txt
maxjeblick 76d06bb
use env file as default
maxjeblick 58a9359
disable keyring if it is not working
maxjeblick f14523d
disable keyring after 3 seconds
maxjeblick ae91449
disable keyring after 3 seconds
maxjeblick 35a1a98
use timeout for keyring credential saver
maxjeblick 4ba47a6
fix timeout
maxjeblick 02f1bf6
fix timeout
maxjeblick 6d12cfb
fix timeout
maxjeblick 691e033
fix format
maxjeblick d6dc681
update readme comment
maxjeblick File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
more type annotations
- Loading branch information
commit a95cb5a4d34516351658293a561710959632227f
There are no files selected for viewing
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
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.
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.
qq, what is the difference between
app_utils > sections > settings.py
vsapp_utils > utils > setting_utils.py
? I wonder if they can be merged then you can revertfrom app_utils.utils.utils import X
. utils.utils.utils looks a bit weird 😅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.
setting_utils.py
contains the backend logic associated with saving and loading the user settings/secrets.settings.py
contains the rendering/routing of the settings page itself.utils.py
contains utils for everything else frontend related.At some point,
utils.py
should probably be split up into multiple files, as it was done forllm_studio
utils.I'd keep the split into
utils
andsetting_utils
as is to start the refactoring ofutils.py
.Regarding the naming:
app_utils.utils.utils
should probably bewave_app.utils.generic_utils
or similar, that is,app_utils
as a folder name is also a bit misleading.Uh oh!
There was an error while loading. Please reload this page.
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.
I see. I think we can do the following steps to make it more tidy:
Doesn't look complicated. Wdyt doing this in another PR?
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.
Yeah, I agree that renaming/moving components makes sense, in particular, for the frontend/wave part.
Let's probably address this in another PR.