Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose configs and files as API in code #2

Open
IljaN opened this issue Aug 27, 2021 · 0 comments
Open

Expose configs and files as API in code #2

IljaN opened this issue Aug 27, 2021 · 0 comments

Comments

@IljaN
Copy link
Contributor

IljaN commented Aug 27, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant