ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/Makefile

49 lines
1.5 KiB
Makefile
Raw Normal View History

make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
WEBSITE_REPO=github.com/hashicorp/terraform-website
Fix missing VERSION for running make website
2020-08-12 19:24:03 +02:00
VERSION?="0.3.44"
Initial work on config
2014-05-23 01:56:28 +02:00
Comment Makefile
2015-01-27 03:19:22 +01:00
# generate runs `go generate` to build the dynamically generated
build: Take protoc out of the "go generate" path Since protoc is not go-gettable, and most development tasks in Terraform won't involve recompiling protoc files anyway, we'll use a separate mechanism for these. This way "go generate" only depends on things we can "go get" in the "make tools" target. In a later commit we should also in some way specify a particular version of protoc to use so that we don't get "flapping" regenerations as developers work with different versions, but the priority here is just to make "make generate" minimally usable again to restore the dev workflow documented in the README. This also includes some updates that resulted from running "make generate" and "make protobuf" after those Makefile changes were in place.
2018-10-18 18:27:48 +02:00
# source files, except the protobuf stubs which are built instead with
# "make protobuf".
Version tools per Go convention under tools.go
2019-10-17 22:17:23 +02:00
generate:
remove vendor from some tooling
2020-09-23 22:57:36 +02:00
go generate ./...
helper/schema: generate strings for ValueType
2015-01-11 00:51:53 +01:00
build: Take protoc out of the "go generate" path Since protoc is not go-gettable, and most development tasks in Terraform won't involve recompiling protoc files anyway, we'll use a separate mechanism for these. This way "go generate" only depends on things we can "go get" in the "make tools" target. In a later commit we should also in some way specify a particular version of protoc to use so that we don't get "flapping" regenerations as developers work with different versions, but the priority here is just to make "make generate" minimally usable again to restore the dev workflow documented in the README. This also includes some updates that resulted from running "make generate" and "make protobuf" after those Makefile changes were in place.
2018-10-18 18:27:48 +02:00
# We separate the protobuf generation because most development tasks on
# Terraform do not involve changing protobuf files and protoc is not a
# go-gettable dependency and so getting it installed can be inconvenient.
#
build: Centralize our protobuf compilation steps We have a few different .proto files in this repository that all need to get recompiled into .pb.go files each time we change them, but we were previously handling that with some scripts that just assumed that protoc and the relevant plugins were already installed on the system somewhere, at the right versions. In practice we've been constantly flopping between different versions of these tools due to folks having different versions installed in their development environments. In particular, the state of the .pb.go files in the prior commit wasn't reproducible by any single version of the tools because they've all slightly diverged from one another. In the interests of being more consistent here and avoiding accidental inconsistencies, we'll now centralize the protocol buffer compile steps all into a single tool that knows how to fetch and install the expected versions of the various tools we need and then run those tools with the right options to get a stable result. If we want to upgrade to either a newer protoc or a newer protoc-gen-go in future then we'll do that in a central location and update all of the .pb.go files at the same time, so that we're always consistently tracking the same version of protocol buffers everywhere. While doing this I attempted to keep as close as possible to the toolchain we'd most recently used, but since they were not consistent with each other they've now all changed which version numbers they record at minimum, and the planproto stub in particular now also has a slightly different descriptor serialization but is otherwise offering the same API.
2021-08-21 01:07:18 +02:00
# If you are working on changes to protobuf interfaces, run this Makefile
# target to be sure to regenerate all of the protobuf stubs using the expected
# versions of protoc and the protoc Go plugins.
build: Take protoc out of the "go generate" path Since protoc is not go-gettable, and most development tasks in Terraform won't involve recompiling protoc files anyway, we'll use a separate mechanism for these. This way "go generate" only depends on things we can "go get" in the "make tools" target. In a later commit we should also in some way specify a particular version of protoc to use so that we don't get "flapping" regenerations as developers work with different versions, but the priority here is just to make "make generate" minimally usable again to restore the dev workflow documented in the README. This also includes some updates that resulted from running "make generate" and "make protobuf" after those Makefile changes were in place.
2018-10-18 18:27:48 +02:00
protobuf:
build: Centralize our protobuf compilation steps We have a few different .proto files in this repository that all need to get recompiled into .pb.go files each time we change them, but we were previously handling that with some scripts that just assumed that protoc and the relevant plugins were already installed on the system somewhere, at the right versions. In practice we've been constantly flopping between different versions of these tools due to folks having different versions installed in their development environments. In particular, the state of the .pb.go files in the prior commit wasn't reproducible by any single version of the tools because they've all slightly diverged from one another. In the interests of being more consistent here and avoiding accidental inconsistencies, we'll now centralize the protocol buffer compile steps all into a single tool that knows how to fetch and install the expected versions of the various tools we need and then run those tools with the right options to get a stable result. If we want to upgrade to either a newer protoc or a newer protoc-gen-go in future then we'll do that in a central location and update all of the .pb.go files at the same time, so that we're always consistently tracking the same version of protocol buffers everywhere. While doing this I attempted to keep as close as possible to the toolchain we'd most recently used, but since they were not consistent with each other they've now all changed which version numbers they record at minimum, and the planproto stub in particular now also has a slightly different descriptor serialization but is otherwise offering the same API.
2021-08-21 01:07:18 +02:00
go run ./tools/protobuf-compile .
build: Take protoc out of the "go generate" path Since protoc is not go-gettable, and most development tasks in Terraform won't involve recompiling protoc files anyway, we'll use a separate mechanism for these. This way "go generate" only depends on things we can "go get" in the "make tools" target. In a later commit we should also in some way specify a particular version of protoc to use so that we don't get "flapping" regenerations as developers work with different versions, but the priority here is just to make "make generate" minimally usable again to restore the dev workflow documented in the README. This also includes some updates that resulted from running "make generate" and "make protobuf" after those Makefile changes were in place.
2018-10-18 18:27:48 +02:00
Make gofmt errors fail build and add `make fmt` We may want to consider requiring `gofmt -s` compliance in future builds, but for now we just use `gofmt`.
2015-12-17 18:21:43 +01:00
fmtcheck:
@sh -c "'$(CURDIR)/scripts/gofmtcheck.sh'"
add staticcheck make target cleanup the old fmtcheck script while we're in here
2020-12-02 18:02:33 +01:00
staticcheck:
@sh -c "'$(CURDIR)/scripts/staticcheck.sh'"
build: Add exhaustive switch statement lint For now, only check the JSON views package, since this was the instance that most recently tripped us up. There are a few dozen failures elsewhere in Terraform which would need to be addressed before expanding this to other packages.
2021-09-24 21:02:30 +02:00
exhaustive:
@sh -c "'$(CURDIR)/scripts/exhaustive.sh'"
make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
website:
update make website workflow
2021-12-17 01:10:17 +01:00
@echo "==> Downloading latest Docker image..."
@docker pull hashicorp/terraform-website:full
make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
@echo "==> Starting core website in Docker..."
@docker run \
--interactive \
--rm \
--tty \
update make website workflow
2021-12-17 01:10:17 +01:00
--workdir "/website" \
--volume "$(shell pwd):/website/ext/terraform" \
--publish "3000:3000" \
hashicorp/terraform-website:full \
npm start
make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
Disallow parallelism in Makefile
2017-02-18 00:31:20 +01:00
# disallow any parallelism (-j) for Make. This is necessary since some
# commands during the build process create temporary files that collide
# under parallel conditions.
.NOTPARALLEL:
add staticcheck make target cleanup the old fmtcheck script while we're in here
2020-12-02 18:02:33 +01:00
.PHONY: fmtcheck generate protobuf website website-test staticcheck