Skip to content

deepcopy: gen: match Go 1.17 build tag format#1

Merged
christarazi merged 1 commit intochristarazi:masterfrom
tklauser:pr/tklauser/add-go-build-tags
Sep 7, 2021
Merged

deepcopy: gen: match Go 1.17 build tag format#1
christarazi merged 1 commit intochristarazi:masterfrom
tklauser:pr/tklauser/add-go-build-tags

Conversation

@tklauser
Copy link
Copy Markdown

@tklauser tklauser commented Sep 6, 2021

Cherry-pick of kubernetes-sigs#595 until it is merged upstream and this fork is rebased on top.

Also see cilium/cilium#17190 (comment) and cilium/cilium#17322 for context.


The Go team has started the process of replacing the old "// +build"
constraints with the new "//go:build" constraints. See the design
doc for more details here:

https://go.googlesource.com/proposal/+/master/design/draft-gobuild.md

What is relevant is that in Go 1.17, gofmt now synchronizes the two
styles. In particular, if gofmt is run against a deepcopy generated
file, it will add a new "//go:build" constraint.

See https://golang.org/doc/go1.17#gofmt for details.

This PR intends to make it so that the generated code is compliant with
the new gofmt style.

The Go team has started the process of replacing the old "// +build"
constraints with the new "//go:build" constraints. See the design
doc for more details here:

https://go.googlesource.com/proposal/+/master/design/draft-gobuild.md

What is relevant is that in Go 1.17, gofmt now synchronizes the two
styles. In particular, if gofmt is run against a deepcopy generated
file, it will add a new "//go:build" constraint.

See https://golang.org/doc/go1.17#gofmt for details.

This PR intends to make it so that the generated code is compliant with
the new gofmt style.

Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
@christarazi christarazi merged commit aa94049 into christarazi:master Sep 7, 2021
@tklauser tklauser deleted the pr/tklauser/add-go-build-tags branch September 7, 2021 07:50
christarazi added a commit to christarazi/cilium that referenced this pull request Dec 8, 2021
Move the fork of controller-tools from my personal fork to be officially
part of the Cilium repo.

Along the way, add the commit from
christarazi/controller-tools#1 to the v0.6.2
branch.

Signed-off-by: Chris Tarazi <chris@isovalent.com>
tklauser pushed a commit to cilium/cilium that referenced this pull request Dec 16, 2021
Move the fork of controller-tools from my personal fork to be officially
part of the Cilium repo.

Along the way, add the commit from
christarazi/controller-tools#1 to the v0.6.2
branch.

Signed-off-by: Chris Tarazi <chris@isovalent.com>
christarazi added a commit to christarazi/cilium that referenced this pull request Jan 3, 2022
[ upstream commit ddb5482 ]

Move the fork of controller-tools from my personal fork to be officially
part of the Cilium repo.

Along the way, add the commit from
christarazi/controller-tools#1 to the v0.6.2
branch.

Signed-off-by: Chris Tarazi <chris@isovalent.com>
Signed-off-by: Chris Tarazi <chris@isovalent.com>
christarazi added a commit to cilium/cilium that referenced this pull request Jan 5, 2022
[ upstream commit ddb5482 ]

Move the fork of controller-tools from my personal fork to be officially
part of the Cilium repo.

Along the way, add the commit from
christarazi/controller-tools#1 to the v0.6.2
branch.

Signed-off-by: Chris Tarazi <chris@isovalent.com>
Signed-off-by: Chris Tarazi <chris@isovalent.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants