terraform

Commit Graph

Author	SHA1	Message	Date
yuriy	08fb9078ea	Update aws-sdk-go dependency to support new region (Jakarta)	4 years ago
Martin Atkins	74761b2f8b	getmodules: Use go-getter v1.5.10 and return to upstream GitGetter There was an unintended regression in go-getter v1.5.9's GitGetter which caused us to temporarily fork that particular getter into Terraform to expedite a fix. However, upstream v1.5.10 now includes a functionally-equivalent fix and so we can heal that fork by upgrading. We'd also neglected to update the Module Sources docs when upgrading to go-getter v1.5.9 originally and so we were missing documentation about the new "depth" argument to enable shadow cloning, which I've added retroactively here along with documenting its restriction of only supporting named refs. This new go-getter release also introduces a new credentials-passing method for the Google Cloud Storage getter, and so we must incorporate that into the Terraform-level documentation about module sources.	4 years ago
Martin Atkins	b0ff17ef2a	getmodules: Inline our own fork of getter.GitGetter This is a pragmatic temporary solution to allow us to more quickly resolve an upstream regression in go-getter locally within Terraform, so that the work to upstream it for other callers can happen asynchronously and with less time pressure. This commit doesn't yet include any changes to address the bug, and instead aims to be functionally equivalent to getter.GitGetter. A subsequent commit will then address the regression, so that the diff of that commit will be easier to apply later to the upstream to get the same effect there.	4 years ago
Brandon Croft	ced4f5500c	update go-tfe to v0.21.0	4 years ago
James Bardin	09291295e2	update hcl@v2.11.1	4 years ago
James Bardin	5facaf8970	update hcl@v2.11.0	4 years ago
Krista LaFentres	2c29a05053	Fix go.mod issues by running go mod tidy -go=1.16 && go mod tidy -go=1.17	4 years ago
tombuildsstuff	bf6c7c0381	go mod tidy/vendor: hamilton is now directly used	4 years ago
tombuildsstuff	0272249f47	go mod vendor/go mod tidy	4 years ago
tombuildsstuff	cf56f42328	dependencies: upgrading to v0.18.0 of github.com/hashicorp/go-azure-helpers	4 years ago
James Bardin	ac52f5135a	update k8s packages from retracted module Use the latest k8s.io packages from v0.21	4 years ago
Barrett Clark	5ef82ddd2f	Cloud: fix e2e tests - Fix tests and remove commented code - Remove parallel for some flaky tests - Add README	4 years ago
Brandon Croft	9441666d9a	Merge pull request #29903 from hashicorp/pull-mock-gotfe-changes Pull changes made to mocks in go-tfe	4 years ago
Brandon Croft	051bf5df7e	update to go-tfe@tfc-integration	4 years ago
kmoe	64635edfb9	Merge pull request #29885 from hashicorp/kmoe/more-init-interrupts command: make module installation interruptible	4 years ago
Katy Moe	7022876494	bump go-getter to v1.5.9	4 years ago
uturunku1	9ef9f97121	pull go tfe changes from main branch	4 years ago
James Bardin	ca6d3cf50f	update go-cty cty: The documented definition and comparison logic of cty.Number is now refined to acknowledge that its true range is limited only to values that have both a binary floating point and decimal representation, because cty values are primarily designed to traverse JSON serialization where numbers are always defined as decimal strings. In particular, that means that two cty.Number values now always compare as equal if their representation in JSON (under cty's own JSON encoder) would be equal, even though the decimal approximation we use for that conversion is slightly lossy. This pragmatic compromise avoids confusing situations where a round-trip through JSON serialization (or other serializations that use the same number format) may produce a value that doesn't compare equal to the original. This new definition of equals should not cause any significant behavior change for any integer in our in-memory storage range, but may cause some fractional values to compare equal where they didn't before if they differ only by a small fraction.	5 years ago
James Bardin	81e709d185	Merge pull request #29825 from hashicorp/jbardin/no-panicwrap Remove the use of panicwrap in the Terraform CLI	5 years ago
Chris Arcand	85f0bc6198	Update go-tfe to e52963e	5 years ago
Omar Ismail	dfb4609be2	Backend State Migration from cloud to cloud. * Add test for tfc to tfc mgiration * Fix old tests, and remove unused code.	5 years ago
Brandon Croft	0bae48bc01	update to tfc-integration branch of go-tfe	5 years ago
Omar Ismail	dd856f8a1b	Add run variables to cloud plan operations from non-file sources Run variables allow the run API to accept input variables not found in the configuration slug (the file-based ones plus workspace vars)	5 years ago
Omar Ismail	55fc590904	Teraform Cloud Backend State Migration * determining source or destination to cloud * handling single to single state migrations to cloud, using a name strategy or a tags strategy * Add end-to-end tests for state migration.	5 years ago
Omar Ismail	a387af6c61	Add auto-approve logic, e2e tests	5 years ago
Chris Arcand	471dd479e8	Update go-tfe to 26689e These changes include additions to fulfill the interface for the client mock, plus moving all that logic (which needn't be duplicated across both the remote and cloud packages) over to the cloud package under a dedicated mock client file.	5 years ago
James Bardin	622c4df14c	remove the use of panicwrap Stop using panicwrap, and execute terraform in the main process.	5 years ago
Martin Atkins	7d3074df46	go.mod: go get github.com/mitchellh/go-wordwrap@v1.0.1	5 years ago
Martin Atkins	39779e7021	backend/remote-state/cos: Don't use github.com/likexian/gokit We don't use this library anywhere else in Terraform, and this backend was using it only for trivial helpers that are easy to express inline anyway. The new direct code is also type-checkable, whereas these helper functions seem to be written using reflection. This gives us one fewer dependency to worry about and makes the test code for this backend follow a similar assertions style as the rest of this codebase.	5 years ago
dependabot[bot]	8946d7ff20	build(deps): bump github.com/golang/protobuf from 1.5.0 to 1.5.2 Bumps [github.com/golang/protobuf](https://github.com/golang/protobuf) from 1.5.0 to 1.5.2. - [Release notes](https://github.com/golang/protobuf/releases) - [Commits](https://github.com/golang/protobuf/compare/v1.5.0...v1.5.2) --- updated-dependencies: - dependency-name: github.com/golang/protobuf dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
Martin Atkins	88bddd7143	go.mod: go get go get golang.org/x/tools@v0.1.7 This also transitively upgrades golang.org/x/sys and golang.org/x/net, but there do not seem to be any significant changes compared to the commits we were previously using.	5 years ago
dependabot[bot]	b0d10c9857	build(deps): bump github.com/xanzy/ssh-agent from 0.2.1 to 0.3.1 Bumps [github.com/xanzy/ssh-agent](https://github.com/xanzy/ssh-agent) from 0.2.1 to 0.3.1. - [Release notes](https://github.com/xanzy/ssh-agent/releases) - [Commits](https://github.com/xanzy/ssh-agent/compare/v0.2.1...v0.3.1) --- updated-dependencies: - dependency-name: github.com/xanzy/ssh-agent dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
dependabot[bot]	051629d74a	build(deps): bump github.com/agext/levenshtein from 1.2.2 to 1.2.3 Bumps [github.com/agext/levenshtein](https://github.com/agext/levenshtein) from 1.2.2 to 1.2.3. - [Release notes](https://github.com/agext/levenshtein/releases) - [Commits](https://github.com/agext/levenshtein/compare/v1.2.2...v1.2.3) --- updated-dependencies: - dependency-name: github.com/agext/levenshtein dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
Martin Atkins	02ca4e970c	go.mod: replace github.com/dgrijalva/jwt-go with .../golang-jwt/jwt CVE-2020-26160 is a high-severity advisory reported against this module. The dgrijalva package is no longer maintained but our legacy etcv2 backend depends on it indirectly, via go.etcd.io/etcd/client. The golang-jwt package is the blessed successor of the original, and has a v3 line which is compatible with the v3 line of dgrijalva, and so through this replace we can get a fix for the advisory without other significant behavior change. We've preserved the etcdv2 backend as-is on a best-effort basis in order to support anyone who is already using it, but recommend that users switch to etcdv3 or to some other backend for ongoing use. We also have future plans to make state storage be a matter for provider plugins rather than built in to Terraform CLI, at which point this backend will either become obsolete or be factored out into its own plugin, at which point we can remove this "replace" directive and the associated dependency altogether.	5 years ago
dependabot[bot]	2fd5ca3767	build(deps): bump honnef.co/go/tools from 0.0.1-2020.1.4 to 0.3.0-0.dev Bumps [honnef.co/go/tools](https://github.com/dominikh/go-tools) from 0.0.1-2020.1.4 to 0.3.0-0.dev. - [Release notes](https://github.com/dominikh/go-tools/releases) - [Commits](https://github.com/dominikh/go-tools/compare/v0.0.1-2020.1.4...v0.3.0-0.dev) --- updated-dependencies: - dependency-name: honnef.co/go/tools dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
Martin Atkins	55f0d06314	go.mod: go get github.com/lib/pq@v1.10.3 This is just a routine upgrade to the latest v1 release.	5 years ago
dependabot[bot]	eec4a838e0	Bump github.com/mitchellh/copystructure from 1.0.0 to 1.2.0 Bumps [github.com/mitchellh/copystructure](https://github.com/mitchellh/copystructure) from 1.0.0 to 1.2.0. - [Release notes](https://github.com/mitchellh/copystructure/releases) - [Commits](https://github.com/mitchellh/copystructure/compare/v1.0.0...v1.2.0) --- updated-dependencies: - dependency-name: github.com/mitchellh/copystructure dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
dependabot[bot]	2dd15caf87	Bump github.com/hashicorp/go-plugin from 1.4.1 to 1.4.3 Bumps [github.com/hashicorp/go-plugin](https://github.com/hashicorp/go-plugin) from 1.4.1 to 1.4.3. - [Release notes](https://github.com/hashicorp/go-plugin/releases) - [Commits](https://github.com/hashicorp/go-plugin/compare/v1.4.1...v1.4.3) --- updated-dependencies: - dependency-name: github.com/hashicorp/go-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>	5 years ago
Martin Atkins	2e6b6e9a6b	go.mod: go get google.golang.org/protobuf@v1.27.1	5 years ago
James Bardin	94ed6a0c84	update the go.mod format for go1.17.2	5 years ago
Alisdair McDiarmid	e09bad76ff	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.	5 years ago
James Bardin	5eb7170f70	add staticcheck to tools	5 years ago
Li Kexian	3f876d14d8	fixed tencentcloud tag	5 years ago
Martin Atkins	ce96d82de0	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.	5 years ago
James Bardin	498dc36635	Merge pull request #29421 from hashicorp/jbardin/tencentcloud-cleanup cleanup tencentcloud missing tag	5 years ago
James Bardin	b543705840	cleanup tencentcloud missing tag TencentCloud deleted all their v3 tags, so any system that does not use the global Go proxy will fail to find the github.com/tencentcloud/tencentcloud-sdk-go module source. Update go.mod to point to the specific commit rather than the incompatible and missing version tag.	5 years ago
Graham Davison	e113974fb2	Updates `github.com/hashicorp/aws-sdk-go-base` from 0.6.0 to 0.7.1	5 years ago
Dominik Keil	b764b3f8a6	Bumping AWS GO SDK to 1.38.42 to fix error when an AWS profile uses both SSO config and credential_process at the same time	5 years ago
James Bardin	d3ea864ab3	github.com/zclconf/go-cty@v1.9.1	5 years ago
Martin Atkins	94f4f8e25d	go.mod: Opt in to pruned module graphs Go 1.17 has a new treatment of go.mod where it tracks more indirect dependencies in return for needing to fetch and load fewer transitive go.mod files. This commit opts in to that new treatment and adds all of the additional indirect dependencies which contain packages that Terraform directly or indirectly makes use of. There are more details on what's going on here in the "Lazy Module Loading" design document: http://golang.org/design/36460-lazy-module-loading (the design document was written assuming this would land in Go 1.15, but it actually landed in Go 1.17 and so it's "go 1.17" that selects the new behavior in spite of the examples in that document.)	5 years ago

1 2 3 4 5 ...

354 Commits (fa8a87fab58166de33b7ceeb63bb906bc20bfbb2)