0.3.0

Added routing based on operationID/alias, taskName, service triple as alternative to hash (8-character hex string, i.e. 645236d8).

If operation has alias, it could be used in domain: <operationAlias>-<taskName>-<service>.<baseDomain>, which is suitable for UIs to open in browser. All you need is to specify operation alias, i.e. for SPYT standalone cluster or direct submit.

It's also supported for headers, you can use old option x-yt-taskproxy-id: 645236d8 or new one, specifying values from triple with headers x-yt-taskproxy-operation-id: <operationID>, x-yt-taskproxy-task-name: <taskName>, x-yt-taskproxy-service: <service>. If operation has alias, you can use x-yt-taskproxy-operation-alias: <operationAlias> instead of operation ID header.

Please note that operation aliases, task names and services should match [a-z0-9_]{1,30}$ regexp to avoid problems with using triple in domain.

0.2.2

auto-discovery of SPYT standalone cluster's master restAPI service

0.2.1

Support header x-yt-taskproxy-id as alternative for domain routing

0.2.0

Initial version of Ytsaurus task proxy