Skip to content

One client to both Consume and Produce #5

@Epse

Description

@Epse

It's mildly unpractical to have two separate clients that both need to be instantiated with secrets and keep track of their own token lifetimes. We may want to put this in one class, since the API surface of either is not that large.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions