Skip to content

Plugin SDK for custom auth and transformations #596

Description

@keysersoft

The auth types and the response-mapping modes are both a fixed list. Every so often someone has an upstream that needs a signature scheme we do not implement, or a response shape that neither the select template nor JMESPath can express.

Scope (design first, code later)

  • Where does a plugin run — in-process, or sandboxed? In-process is simple and gives a plugin the credentials.
  • TypeScript first; Python only if there is demand.
  • Two extension points to start: sign an outgoing request, transform an incoming response.

This issue is open for the design discussion. Please do not send an implementation PR before it is settled.

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

    roadmapOn the published roadmap; exempt from the stale bot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions