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
{{ message }}
This repository was archived by the owner on May 15, 2024. It is now read-only.
In a few conversations, the need for Motion to coordinate unsealing of data that's only available in sealed form has come up. This is to facilitate a S3 Glacier like functionality. This feature would require changes in the boost API to programmatically request unsealing, check its progress, etc.
Until further user requirements are clarified, this issue serves as a place holder to further investigate the scope of work.
The text was updated successfully, but these errors were encountered:
I would say this is M2-type functionality. The initial users of motion won't be "glacier-like" salespeople. Moreover reasonable unsealing without UaaS infrastructure is a tenuous proposition...
All in all - while having this functionality as a PoC might be valuable at some point, it is unlikely this will be useful in reality. Definitely not in the M1 version.
In a few conversations, the need for Motion to coordinate unsealing of data that's only available in sealed form has come up. This is to facilitate a S3 Glacier like functionality. This feature would require changes in the boost API to programmatically request unsealing, check its progress, etc.
Until further user requirements are clarified, this issue serves as a place holder to further investigate the scope of work.
The text was updated successfully, but these errors were encountered: