d70f6e3760
What: This change moves project-level bucket metadata encryption information to the volatile section, because it is unlikely to remain in future releases Why: Ultimately, the web user interface will allow bucket management (creation, removal, etc), but not object management as that requires an encryption key for sure and we don't want to have users give the satellite their encryption keys. At a high level, a (*Project) type should map to all of the things you can do inside the web user interface within a project, which by necessity cannot have an encryption key. So, we really don't want an encryption key in the non-volatile section of this library. |
||
|---|---|---|
| .. | ||
| bootstrap | ||
| certificates | ||
| gateway | ||
| identity | ||
| inspector | ||
| overlay | ||
| s3-benchmark | ||
| satellite | ||
| statreceiver | ||
| storagenode | ||
| storj-sim | ||
| uplink | ||
| versioncontrol | ||