Skip to content

Support API key configuration for Zerox in multi-tenant setup #366

@avirajsingh7

Description

@avirajsingh7

We are currently using Zerox for document transformation in our system. However, Zerox only supports reading the API key from environment variables.

Our platform is multi-tenant, and the API key is scoped per project. This makes it problematic to rely solely on environment variables for API key management.

We already opened a PR in the Zerox repo to add support for passing the API key explicitly instead of always fetching it from environment variables. However, in case we don’t receive a response from the maintainers, we will need to either:

  • Move to another tool that supports this flexibility, or
  • Implement a workaround where each Celery worker handles project-specific API keys.

Context:

Each Celery worker runs in a separate process, which means separate memory and environment, so we can set api_key in env.

Test:
Once fixed this add unit tests for transfomer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions