Skip to content

Expose configs and files as API in code #2

Description

@IljaN

For the "embedding as library use-case" the consumer might want to provide a custom-configuration format (memory,vfs). Currently there is no way to embed lico without having an identifier-registration.yml somewhere on the file-system.

To solve this the configuration should be exposed as map or struct internally.

Also other supporting files like certs and secrets should be passable as an io.Reader or byte[].

Related: Kopano-dev/konnect#24

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