-
Notifications
You must be signed in to change notification settings - Fork 81
/
.golangci.yml
116 lines (104 loc) · 3.36 KB
/
.golangci.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
linters:
disable-all: true
enable:
#- bodyclose
- depguard
- dogsled
- dupl
- errcheck
- errorlint
- copyloopvar
#- gocritic
- gocyclo
- goimports
- goprintffuncname
- gosec
- gosimple
- govet
- gofmt
- ineffassign
- misspell
- noctx
- prealloc
- rowserrcheck
- staticcheck
- stylecheck
- typecheck
- unconvert
- unparam
- unused
- whitespace
- importas
linters-settings:
misspell:
locale: US
goimports:
local-prefixes: github.com/mongodb/mongodb-atlas-kubernetes/v2
depguard:
rules:
all:
deny:
- pkg: io/ioutil
desc: 'io/ioutil package has been deprecated'
issues:
exclude-use-default: false
exclude:
# EXC0001 errcheck: Almost all programs ignore errors on these functions and in most cases it's ok
- Error return value of .((os\.)?std(out|err)\..*|.*Close|.*Flush|os\.Remove(All)?|.*print(f|ln)?|os\.(Un)?Setenv). is not checked
# EXC0002 golint: Annoying issue about not having a comment. The rare codebase has such comments
# - (comment on exported (method|function|type|const)|should have( a package)? comment|comment should be of the form)
# EXC0003 golint: False positive when tests are defined in package 'test'
- func name will be used as test\.Test.* by other packages, and that stutters; consider calling this
# EXC0004 govet: Common false positives
- (possible misuse of unsafe.Pointer|should have signature)
# EXC0005 staticcheck: Developers tend to write in C-style with an explicit 'break' in a 'switch', so it's ok to ignore
# - ineffective break statement. Did you mean to break out of the outer loop
# EXC0006 gosec: Too many false-positives on 'unsafe' usage
- Use of unsafe calls should be audited
# EXC0007 gosec: Too many false-positives for parametrized shell calls
- Subprocess launch(ed with variable|ing should be audited)
# EXC0008 gosec: Duplicated errcheck checks
- (G104|G307)
# EXC0009 gosec: Too many issues in popular repos
# - (Expect directory permissions to be 0750 or less|Expect file permissions to be 0600 or less)
# EXC0010 gosec: False positive is triggered by 'src, err := ioutil.ReadFile(filename)'
# - Potential file inclusion via variable
# EXC0011 stylecheck: Annoying issue about not having a comment. The rare codebase has such comments
# - (comment on exported (method|function|type|const)|should have( a package)? comment|comment should be of the form)
- at least one file in a package should have a package comment
exclude-rules:
- path: test
linters:
- gocyclo
- gochecknoglobals
- wrapcheck
- nlreturn
- errcheck
- path: cmd/manager/main.go
linters:
- gochecknoglobals
- wrapcheck
- path: test/e2e
linters:
- stylecheck
- noctx
- path: test/helper
linters:
- stylecheck
text: "ST1000:|ST1001:|ST1003:"
- path: test/helper/e2e/appclient
linters:
- noctx
- path: pkg/controller
linters:
- prealloc
- dupl
- unparam
- path: pkg/controller/atlasdatabaseuser/connectionsecrets
linters:
- prealloc
- path: pkg/util/testutil/
linters:
- stylecheck
max-issues-per-linter: 0
max-same-issues: 0