Robin Moffatt

@nwinkler nice tips, thanks for sharing!

I picked the wrong env var to try and determine if Connect's REST endpoint was running HTTPS. `CONNECT_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM` is actually nothing to do with it. From what I can tell...

> Should the healthcheck be implementing the same defaults that connect does, i.e. ${CONNECT_REST_PORT:-8083} Yes, that sounds sensible

@authorjapps please can you describe what your issue is? And provide details about your environment—versions, deployment approach e.g. Docker or not, etc.

Re. the CLI, you need to provide the KSQL Server address for it to connect to. So based on https://github.com/authorjapps/zerocode/blob/master/docker/compose/kafka-schema-registry.yml your test should be invoked `ksql http://ksql-server:8088`, not just `ksql`....

You can put what you want onto a Kafka topic, and using the Consumer API you can read what you want. KSQL is a higher level abstraction, and as such...

Feel free to head over to http://cnfl.io/slack and the #ksql channel for more help on this if you want.

I just looked at this a bit more. If I launch the CLI (0.13) and once it's started, hold Ctrl-C, I get the error. ``` =========================================== = _ _ ____...

(_To help others find this issue, the latest (0.14) version of the message is_ `N-way joins do not support multiple occurrences of the same source`) ---- I also tried duplicating...

ping @MichaelDrogalis @ybyzek for input here plz