Webhook: go build fails with 'undefined: tls.CipherSuites'

Created on 8 Jul 2020  路  6Comments  路  Source: adnanh/webhook

go build fails with

[ansible@awx2 webhook]$ go build github.com/adnanh/webhook
go: downloading github.com/gorilla/mux v1.7.3
go: downloading github.com/go-chi/chi v4.0.2+incompatible
go: downloading gopkg.in/fsnotify.v1 v1.4.2
go: downloading github.com/dustin/go-humanize v1.0.0
go: downloading github.com/gofrs/uuid v3.2.0+incompatible
go: downloading github.com/clbanning/mxj v1.8.4
go: downloading github.com/ghodss/yaml v1.0.0
go: extracting github.com/dustin/go-humanize v1.0.0
go: extracting github.com/gofrs/uuid v3.2.0+incompatible
go: extracting gopkg.in/fsnotify.v1 v1.4.2
go: extracting github.com/gorilla/mux v1.7.3
go: extracting github.com/ghodss/yaml v1.0.0
go: downloading gopkg.in/yaml.v2 v2.0.0-20170812160011-eb3733d160e7
go: downloading golang.org/x/sys v0.0.0-20191228213918-04cbcbbfeed8
go: extracting github.com/go-chi/chi v4.0.2+incompatible
go: extracting gopkg.in/yaml.v2 v2.0.0-20170812160011-eb3733d160e7
go: extracting github.com/clbanning/mxj v1.8.4
go: extracting golang.org/x/sys v0.0.0-20191228213918-04cbcbbfeed8
go: finding github.com/go-chi/chi v4.0.2+incompatible
go: finding github.com/clbanning/mxj v1.8.4
go: finding github.com/gorilla/mux v1.7.3
go: finding github.com/dustin/go-humanize v1.0.0
go: finding gopkg.in/fsnotify.v1 v1.4.2
go: finding github.com/gofrs/uuid v3.2.0+incompatible
go: finding github.com/ghodss/yaml v1.0.0
go: finding gopkg.in/yaml.v2 v2.0.0-20170812160011-eb3733d160e7
go: finding golang.org/x/sys v0.0.0-20191228213918-04cbcbbfeed8
# github.com/adnanh/webhook
./tls.go:11:20: undefined: tls.CipherSuites
./tls.go:53:15: undefined: tls.CipherSuites

Version is:

go version go1.13.11 linux/amd64

Any ideas ?

bug

Most helpful comment

Based on README.md - v1.12 is enough. If 1.14 is the new minimum, the README.md should be updated

All 6 comments

We require at least Go 1.14 now.

Based on README.md - v1.12 is enough. If 1.14 is the new minimum, the README.md should be updated

hey, it still says 1.12 in the README.md

Thankfully it's fixed in Development branch... I am quite curious how long it will take to be moved to the master.

@adnanh,
Do you think you can ship v2.7.1 soon?

@moorereason shipped the 2.8.0, I'll update all milestone references from 2.7.1 to 2.8.0

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nkv16786 picture nkv16786  路  3Comments

alexw22 picture alexw22  路  3Comments

Gareth-3aaa picture Gareth-3aaa  路  4Comments

wranitzky picture wranitzky  路  6Comments

foosinn picture foosinn  路  5Comments