Craig Dunn
Craig Dunn
Jerakia has the ability to give different API tokens to different services but currently they all have the same level of access, it would be useful to be able to...
Tokens should be used to restrict/allow certain things - especially access to the encryption provider * Ideas * OAuth2 ?
This is kind of annoying as `-q` is meant to only return the token (for scripted captures...etc) - assuming this is a ruby dependency that needs a version bump.. ```...
As discussed in #116 - namespace has been made optional in other areas (CLI...etc) so the API should not enforce this parameter. This removes the mandatory parameter check for the...
The JERAKIA_CONFIG environment variable that is used to override the default location of jerakia.yaml is not documented on the site. This needs to be made clear as it's a useful...
The "config" subcommand should also accept the "--config" flag for validating non-standard config files against defaults.
A consul datasource should be shipped with Jerakia by default. This should be fairly basic to implement, though we should try not to duplicate most of the HTTP datasource to...
Currently schemas are declared at a global level in `jerakia.yaml` which means you cannot have different schemas across different policies and/or lookups. Enabling schemas and their configuration should be a...
For example, serving %{REQUEST_URI} as a string from jerakia requires you do do something horrible like %%{1}{REQUEST_URI} which is very hacky.
Currently missing from http://jerakia.io.... - [ ] Hiera lookup plugins - [ ] Writing custom lookup plugins - [ ] Writing datasources - [x] Encryption response filter (eyaml) - [x]...