Currently, the litmus portal’s backend logs aren’t meaningful and formatted. Also, It’s difficult to find the root cause of any litmus portal component failure by going through the logs.

The requirements of this issue are:

• Use a common go pkg like logrus/glog/klog across all litmus portal’s backend components
• Add meaningful log on the edge cases
• Format the existing log.

List of c

The kuttl cli overrides the testsuite file... with the exception of the test env. (this is a require to fix that).

If the kuttl-test.yaml has a configuration for startControlPlane: true and the cli is started with --start-kind.... the cli override should start kind.

Perhaps we should have an override that allows to point at a cluster (currently it is the default that is selected if no

Hi,

We have installed ArgoCD on OpenShift using the argocd operator and are shipping the logs from the ArgoCD-components to a external log management system, and would like the logs to be structured in json format.

I found that ArgoCD 1.6+ added the option --logformat, and I have indeed tested it successfully by setting the option manually in the Deployment spec for argocd-server:

 na

Is your feature request related to a problem? Please describe.
The following error shows up in the log when the GitHub webhook is tested:

{"level":"error","ts":1593630175.1589122,"logger":"handler","msg":"could not parse webhook","error":"unknown X-Github-Event in message: ","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/travis/gopath/pkg/mod/github.com/go-logr/zapr@v

It should be somewhat easy to translate from reading .circleci/config.yaml

Description of Issue

After go-config v0.7.0, our operator breaks on startup citing that there is no provider configured.

How to Reproduce

Update the following constraint in Gopkg.toml from 0.7.0 to any later release:

[[constraint]]
  name = "github.com/micro/go-config"
  version = "0.7.0"

Install dependencies and start operat

In #48 there was someone that gave POSTGRES_CLOUD_PROVIDER the value AZURE while it should be Azure. This shouldn't matter and we should run the provided value through ToLower() before we make the comparison.

See: https://github.com/TykTechnologies/tyk-operator/blob/master/docs/api_definitions.md#endpoint-level

Tyk Operator currently does not support allow, block & ignore list Endpoint level middlewares. (nee BlackList, WhiteList, Igno