Replaced 'winston-logfmt' by 'winston' package.

[jeroenvermeulen]

Fixes #2

[paulrostorp]

It's an important requirement to maintain structured logging.
I don't have the bandwidth to fix the logfmt implementation atm, but maybe you could enable the Winston builtin json logger ?

[jeroenvermeulen]

@paulrostorp With the winston package it logs like this:

debug: Starting Bunny CDN Operator...
info: watching resource edgerules.bunny-cdn-operator.com/v1alpha1
info: watching resource storagezones.bunny-cdn-operator.com/v1alpha1
info: watching resource pullzones.bunny-cdn-operator.com/v1alpha1
debug: Bunny CDN Operator started.
debug: Processing change to Pull Zone local-app-cloud...

Isn't that structured enough?

[paulrostorp]

@paulrostorp With the winston package it logs like this:

debug: Starting Bunny CDN Operator...
info: watching resource edgerules.bunny-cdn-operator.com/v1alpha1
info: watching resource storagezones.bunny-cdn-operator.com/v1alpha1
info: watching resource pullzones.bunny-cdn-operator.com/v1alpha1
debug: Bunny CDN Operator started.
debug: Processing change to Pull Zone local-app-cloud...

Isn't that structured enough?

@jeroenvermeulen That isn't a structure log management tools support by default and can index+search easily. Most log management tools have built-in support logfmt and json logs, including Grafana Loki which I use.

Winston's JSON logger will suffice: https://github.com/winstonjs/winston#usage

[jeroenvermeulen]

@paulrostorp Updated PR. Now it logs like this:

{"level":"debug","message":"Starting Bunny CDN Operator..."}
{"level":"info","message":"watching resource edgerules.bunny-cdn-operator.com/v1alpha1"}
{"level":"info","message":"watching resource storagezones.bunny-cdn-operator.com/v1alpha1"}
{"level":"info","message":"watching resource pullzones.bunny-cdn-operator.com/v1alpha1"}
{"level":"debug","message":"Bunny CDN Operator started."}
{"level":"debug","message":"Processing change to Pull Zone local-app-cloud..."}