Skip to content

Rely on the NATS cluster connection status when reporting the Eventing CR status #792

Rely on the NATS cluster connection status when reporting the Eventing CR status

Rely on the NATS cluster connection status when reporting the Eventing CR status #792

Triggered via pull request December 14, 2023 11:15
Status Failure
Total duration 2m 32s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 errors
lint: internal/connection/nats/interfase.go#L4
File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kyma-project/eventing-manager) -s blank -s dot --custom-order (gci)
lint: internal/connection/nats/interfase.go#L5
File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/kyma-project/eventing-manager) -s blank -s dot --custom-order (gci)
lint: internal/connection/nats/nats.go#L11
File is not `gofumpt`-ed (gofumpt)
lint: internal/controller/operator/eventing/controller.go#L50
import "github.com/kyma-project/eventing-manager/internal/connection/nats" has alias "natsconnection" which is not part of config (importas)
lint: internal/controller/operator/eventing/controller.go#L542
File is not `gofumpt`-ed (gofumpt)
lint
issues found