Fix port configuration UX

Fixing port configuration UX as per request from @reitermarkus
now the port is not added through environmental variable, but rather
through logic in the broker host, as the original implementation
in the multiple brokers commit

Signed-off-by: Martin Dekov <mvdekov@gmail.com>

Make the payment topic consistent

Signed-off-by: Richard Gee <richard@technologee.co.uk>

Fix Travis image pushing

Use tag of latest-dev to match .travis.yml

Signed-off-by: Alex Ellis <alexellis2@gmail.com>

Add helm chart to README

Signed-off-by: Alex Ellis <alexellis2@gmail.com>

Wait for populated topicMap before connecting to broker

Before this commit restarting/scaling to 0 and back again with the
kafka-connector would result in any outstanding queued messages being
immediated received by the connector on restart but before
the topicMap sync would have been completed.

This would result in function trigger events being handled before a
target function could be determined, effectively blackhole-ing the
function trigger.

This change delays the kafka-connectors connection to the broker until
a non-empty topicMap is returned, thereby guaranteeing any already
configured functions will be triggered as expected.

Signed-off-by: John McCabe <john@johnmccabe.net>

Create .DEREK.yml

Add Derek

Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>

Delete .DS_Store