Vladimir Klimontovich

Quotas should be managed inside a connector code, not internally. Different APIs has a different subject for quotas, it can be IP address, API key, etc. Runtime should give connector...

Thank you for reporting this! We should implement this via plugins, it doesn't make sense to add this logic to a core processing pipeline. Here's a architecture: ### Give [transforms](https://jitsu.com/docs/configuration/javascript-transform)...

TWIMC, this feature will be in `beta` around 31st of Aug 2020

Great idea! We probably will do it on a new version of [facebook connector written in JavaScript](https://github.com/jitsucom/jitsu-sdk/tree/main/source-connectors). Also, it would probably make sense to introduce a rate limiter which sources...

To be continued at #880, closing this one

A few updates on this issue: * We started to use k8s to run part of Jitsu Cloud (Rotor, Bulker and Igest), so we have a strong foundation * We...

It's time to revisit this given a new architecture of Jitsu Next and the fact that we use Mongo as an underlying storage for user recognition. Here's a preliminary design:...

I'm not sure it's safe to pass `access_token` to frontend for all SSO envs. If we're going to do so at all, this should be made configurable

Would you mind sharing stacktrace?  Also, which version of jitsucom/console image you're using

I'm going to close this one without merging since a new service, `ingest` is now responsible for processing messages