Keith Wall
Keith Wall
Kroxylicious does not currently have a contributor agreement. I think we should adopt DCO to all Kroxylicious repositories. We should use tools such as https://probot.github.io/apps/dco/ to automate the checks that...
Currently `/docs` contains the documentation for the whole project, including all the filters. This approach doesn't really scale. It would be better if modules (and I'm thinking of filters initially)...
**Is your feature request related to a problem? Please describe.** We've currently got duplicated release scripts across the kroxylicious and kroxylicious-junit5-ext. We are burning time manually copying changes to and...
Implementing a second KMS soon would help validate our KMS API design and also help illuminate concerns such as error handling. I have a preference that AWS is next, principally...
`transition-staging-repository-state.sh drop` is used to clean up in the event that the release process fails. It fails itself if the release hasn't got as far as the staging step. `drop`should...
As an Filter author, I wish to have access to the downstream client ip/client principal (SASL, mTLS) of the connected client. Possible use-cases: * an Audit Filter may want to...
Currently the test suite is only exercising the Kroxylicious against the version of Kafka Kroxylicious is built against. We ought to have a test matrix that tests against earlier versions...
Currently the test suite is only exercising the Kroxylicious against the version of Kafka Kroxylicious is build against. We ought to have a test matrix that tests against earlier versions...
**Is your feature request related to a problem? Please describe.** Currently as a user of the metrics of Kroxylicious, I can get an understanding of the number of bytes flowing...
We need tests for encryption key edge cases such as expired keys, wrong key type etc. We should ensure that the system behaves in a reason way, with clear error...