[FEATURE] Routing API

[arttor]

Feature Request

Chorus routing policy have the following structure:

1. KEY: USER + BUCKET [OPTIONAL]
2. VALUE: Destination storage name

Chorus proxy defines destination storage by the following algorithm:

1. Lookup bucket routing policy by proxy s3 request user&bucket.
2. If not found, lookup user routing policy by proxy s3 request user.
3. If not found, return main storage from config.

Problem: currently, chorus routing policy can be sent only implicitly, by creating replication switch. There is no API to configure routing policies directly.

Solution: provide API to configure chorus proxy routing per user/bucket :

• GET all/per user/per bucket - returns proxy routing configuration
• PUT /per user/per bucket - overrides user/bucket routing
• DELETE /per user/per bucket - deletes routing.