Github user kaspersorensen commented on the issue:
    OK so I have been going over this in my mind again and again a few times. 
Couldn't quite make myself remove the tenant concept either :-P At least I feel 
it needs a bit more thought. One of the things I like about it in a URL pattern 
like `/{tenant}/{datastore}`is that it allows for simple authorization schemes 
to grant access to `/{some-tenant}/*` and thereby make someone a tenant 
administator. Similarly of course a particular datastore could be authorized by 
using the URL pattern. Not having any such "outer collection name" means that 
setting up access rules becomes a lot more difficult. Whether it is tenant or 
some other grouping term I don't mind so much. It just feels like a big aid in 
organizing the catalog of datastores.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to