Skip to content

feat: metadata passthrough on render #97

Description

@ajianaz

Demand source: Bannerbear metadata field — an arbitrary string stored + returned. Pipeline use case: carry an internal record ID / trace ID through the render request.

Proposed design:

  • Optional metadata: string (or small object) on CLI/API requests.
  • API JSON response (response_format: json): echo the metadata back.
  • CLI: write to a sidecar .json or a structured log.

Acceptance:

  • POST with metadata -> the JSON response contains the exact same metadata.
  • Without metadata -> the field is absent (not null).

Effort: S. Priority #6.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions