You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there'd be two useful pieces of functionality here:
Basically implement what https://github.com/Pernosco/pernosco-submit/blob/master/pernosco-submit does here. pernosco-submit has a number of dependencies and is a bit of pain to set up - we should be able to just upload directly. The submission process is very similar to our own submission process (in that it's also an S3 upload), but there's some encryption going on.
Add the ability to copy a previously uploaded trace to pernosco, ideally by just doing an S3-side copy, but there may need to be a lambda involved for handling the encryption.
It would be nice to streamline pernosco authentication also. I always have trouble finding my credentials and I think from our experience here, the one click authentication is about what users are willing to tolerate.
I think there'd be two useful pieces of functionality here:
Basically implement what https://github.com/Pernosco/pernosco-submit/blob/master/pernosco-submit does here. pernosco-submit has a number of dependencies and is a bit of pain to set up - we should be able to just upload directly. The submission process is very similar to our own submission process (in that it's also an S3 upload), but there's some encryption going on.
Add the ability to copy a previously uploaded trace to pernosco, ideally by just doing an S3-side copy, but there may need to be a lambda involved for handling the encryption.
It would be nice to streamline pernosco authentication also. I always have trouble finding my credentials and I think from our experience here, the one click authentication is about what users are willing to tolerate.
cc @khuey
The text was updated successfully, but these errors were encountered: