-
Notifications
You must be signed in to change notification settings - Fork 5
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
Vaults general fixes and QOL #340
Labels
development
Standard development
r&d:polykey:core activity 1
Secret Vault Sharing and Secret History Management
Comments
Merged
15 tasks
tegefaulkes
changed the title
Switching to selective imports in vaults domain
Vaults general fixes and QOL
Feb 16, 2022
It would be similar to:
So yea vault map (the in-memory one) would use |
tegefaulkes
added a commit
that referenced
this issue
Feb 21, 2022
|
tegefaulkes
added a commit
that referenced
this issue
Feb 21, 2022
tegefaulkes
added a commit
that referenced
this issue
Feb 21, 2022
|
tegefaulkes
added a commit
that referenced
this issue
Feb 28, 2022
tegefaulkes
added a commit
that referenced
this issue
Mar 9, 2022
tegefaulkes
added a commit
that referenced
this issue
Mar 9, 2022
tegefaulkes
added a commit
that referenced
this issue
Mar 9, 2022
tegefaulkes
added a commit
that referenced
this issue
Mar 9, 2022
teebirdy
added
the
r&d:polykey:core activity 1
Secret Vault Sharing and Secret History Management
label
Jul 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
development
Standard development
r&d:polykey:core activity 1
Secret Vault Sharing and Secret History Management
Specification
This issue relates to general fixes and QOL changes.
Change to selective imports in all relevant domains. And ensure there are no import cycles in the vaults domain.
Additional context
Tasks
VaultId
decoding needs to be checked for iffromMultibase
throws an error. this needs to be fixed.VaultsLog
GRPC method can use the google timestamp type for the timestamp.The text was updated successfully, but these errors were encountered: