List view
- Removal of old-style hashing. We could leave room for multiple encryption methods, but we should probably configure that per pstore-server instead of per object: - Multiple hosts in the config. (Through sections.) And make sure that bash completion still works. - Rework the CLI for more logic. - Add object templates. The basic template would be "password" which only enforces an encrypted password to exist. Other templates could be "ssl" certificates with a public crt and a private key. Or machine with with "ip" (multiple LF delimited) and "location". These templates can be combined. - Template support may increasing multicompany support. Right now there is only admin and non-admin. Do we need more granularity so others can add/edit templates? We possibly need "objectgroups": for starters to group objects together and to give the read/list permissions that now the staff users have. pstore -g ysis production-mongo: now we need to enforce objects to be in a group AND move the unique object key to group+identifier. This would make a lot more sense for multicompany usage. We can attach users to a group and quickly/automated add/revoke object permissions within that group. - Property metadata: e.g. for content-type, filename (which is lowercased right now). When filename is set, we could auto-download an entire object into a specified dir. - Search: find property names, find (unencrypted) property contents. Other things that need to be done in the process: - Fix the client-test to be less ugly: - * flushall is okay, but needs to be done on a test_* database - * every test should restart from base instead of from result of previous test
No due date