resilien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
terraform/go.mod

123 lines
5.7 KiB
Modula-2
Raw Normal View History

vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-25 01:13:05 +02:00
module github.com/hashicorp/terraform
require (
backend: Add service account impersonation to GCS Backend and update the docs (#26700)
2020-11-06 15:06:07 +01:00
cloud.google.com/go/storage v1.10.0
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/Azure/azure-sdk-for-go v52.5.0+incompatible
github.com/Azure/go-autorest/autorest v0.11.18
communicator/winrm: include configured timeout in winrm server * upgrade windows dependencies * communicator/winrm: include configured timeout in winrm server
2020-06-25 14:41:09 +02:00
github.com/Azure/go-ntlmssp v0.0.0-20200615164410-66371956d46c // indirect
github.com/ChrisTrenkamp/goxpath v0.0.0-20190607011252-c5096ec8773d // indirect
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/abdullin/seq v0.0.0-20160510034733-d5467c17e7af // indirect
vendor: github.com/agext/levenshtein@v1.2.2
2019-02-22 23:15:02 +01:00
github.com/agext/levenshtein v1.2.2
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/aliyun/alibaba-cloud-sdk-go v0.0.0-20190329064014-6e358769c32a
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/aliyun/aliyun-oss-go-sdk v0.0.0-20190103054945-8205d1f41e70
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/aliyun/aliyun-tablestore-go-sdk v4.1.2+incompatible
upgrade go-cidr to v1.1.0
2020-07-08 16:57:57 +02:00
github.com/apparentlymart/go-cidr v1.1.0
vendor: github.com/apparentlymart/go-dump@042adf3cf4a0 go get github.com/apparentlymart/go-dump@042adf3cf4a0 go mod tidy go mod vendor
2019-02-21 09:45:27 +01:00
github.com/apparentlymart/go-dump v0.0.0-20190214190832-042adf3cf4a0
command: Experimental "terraform test" command This is just a prototype to gather some feedback in our ongoing research on integration testing of Terraform modules. The hope is that by having a command integrated into Terraform itself it'll be easier for interested module authors to give it a try, and also easier for us to iterate quickly based on feedback without having to coordinate across multiple codebases. Everything about this is subject to change even in future patch releases. Since it's a CLI command rather than a configuration language feature it's not using the language experiments mechanism, but generates a warning similar to the one language experiments generate in order to be clear that backward compatibility is not guaranteed.
2021-02-09 01:03:15 +01:00
github.com/apparentlymart/go-shquot v0.0.1
vendor: upgrade go-userdirs library to fix openBSD crash (#26249) Fixes #26175
2020-09-15 20:14:25 +02:00
github.com/apparentlymart/go-userdirs v0.0.0-20200915174352-b0c018a67c13
fix: update go-versions with improved error handling closes #26516 Signed-off-by: Carlos Alexandro Becker <caarlos0@gmail.com>
2020-10-10 13:36:16 +02:00
github.com/apparentlymart/go-versions v1.0.1
vendor: github.com/armon/circbuf@5111143e8da2 go get github.com/armon/circbuf@5111143e8da2 go mod tidy go mod vendor
2019-02-21 09:48:13 +01:00
github.com/armon/circbuf v0.0.0-20190214190532-5111143e8da2
deps: Bump github.com/aws/aws-sdk-go@v1.37.0 Changes: ``` * backend/s3: Support for AWS Single-Sign On (SSO) cached credentials ``` Updated via: ``` go get github.com/aws/aws-sdk-go@v1.37.0 go mod tidy ``` Please note that Terraform CLI will not initiate or perform the AWS SSO login flow. It is expected that you have already performed the SSO login flow using AWS CLI using the `aws sso login` command, or by some other mechanism before executing Terraform. More precisely, this credential handling must find a valid non-expired access token for the AWS SSO user portal URL in `~/.aws/sso/cache`. If a cached token is not found, is expired, or the file is malformed an error will be returned. You can use configure AWS SSO credentials from the AWS shared configuration file by specifying the required keys in the profile: ``` sso_account_id sso_region sso_role_name sso_start_url ``` For example, the following defines a profile "devsso" and specifies the AWS SSO parameters that defines the target account, role, sign-on portal, and the region where the user portal is located. Note: all SSO arguments must be provided, or an error will be returned. ``` [profile devsso] sso_start_url = https:my-sso-portal.awsapps.com/start sso_role_name = SSOReadOnlyRole sso_region = us-east-1 sso_account_id = 123456789012 ``` Additional Resources * [Configuring the AWS CLI to use AWS Single Sign-On](https:docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html) * [AWS Single Sign-On User Guide](https:docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html)
2021-01-28 21:22:01 +01:00
github.com/aws/aws-sdk-go v1.37.0
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/baiyubin/aliyun-sts-go-sdk v0.0.0-20180326062324-cfa1a18b161f // indirect
command/login: Require "yes" to confirm This is for consistency with other commands which use prompts, all of which require "yes" rather than "y" to confirm. We also migrate the login command to use UIInput, which now supports securely asking for passwords or secrets via the speakeasy library.
2020-06-24 20:47:59 +02:00
github.com/bgentry/speakeasy v0.1.0
lang/funcs: Switch fileset() function glob implementation to github.com/bmatcuk/doublestar to support additional glob patterns This allows the usage of the glob patterns `**` and `{alternative1,...}` to simplify Terraform configuration logic for more complex file matching.
2019-08-31 02:14:38 +02:00
github.com/bmatcuk/doublestar v1.1.5
vendor: go get github.com/chzyer/readline@master This new version includes Solaris support, the lack of which previously caused us to disable readline-using features ("terraform console") on Solaris builds.
2019-08-10 00:49:03 +02:00
github.com/chzyer/readline v0.0.0-20180603132655-2972be24d48e
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
github.com/coreos/go-systemd v0.0.0-20181012123002-c6f51f82210d // indirect
go.mod,backend: update coreos/etcd dependency to release-3.4 branch etcd rewrote its import path from coreos/etcd to go.etcd.io/etcd. Changed the imports path in this commit, which also updates the code version. This lets us remove the github.com/ugorji/go/codec dependency, which was pinned to a fairly old version. The net change is a loss of 30,000 lines of code in the vendor directory. (I first noticed this problem because the outdated go/codec dependency was causing a dependency failure when I tried to put Terraform and another project in the same vendor directory.) Note the version shows up funkily in go.mod, but I verified visually it's the same commit as the "release-3.4" tag in github.com/coreos/etcd. The etcd team plans to fix the release version tagging in v3.5, which should be released soon.
2021-01-27 23:04:52 +01:00
github.com/coreos/pkg v0.0.0-20180928190104-399ea9e2e55f
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
github.com/davecgh/go-spew v1.1.1
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/dylanmei/iso8601 v0.1.0 // indirect
vendor: github.com/dylanmei/winrmtest@99b7fe2fddf1
2019-02-26 19:22:15 +01:00
github.com/dylanmei/winrmtest v0.0.0-20190225150635-99b7fe2fddf1
deps: Bump github.com/go-test/deep to 1.0.3
2019-08-21 12:32:13 +02:00
github.com/go-test/deep v1.0.3
communicator/winrm: include configured timeout in winrm server * upgrade windows dependencies * communicator/winrm: include configured timeout in winrm server
2020-06-25 14:41:09 +02:00
github.com/gofrs/uuid v3.3.0+incompatible // indirect
add impersonation
2021-04-07 00:58:24 +02:00
github.com/golang/mock v1.5.0
update proto packages
2020-12-01 20:04:17 +01:00
github.com/golang/protobuf v1.4.3
add impersonation
2021-04-07 00:58:24 +02:00
github.com/google/go-cmp v0.5.5
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/google/uuid v1.2.0
Update dependencies
2020-04-25 08:41:54 +02:00
github.com/gophercloud/gophercloud v0.10.1-0.20200424014253-c3bfe50899e5
github.com/gophercloud/utils v0.0.0-20200423144003-7c72efc7435d
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
github.com/gopherjs/gopherjs v0.0.0-20181017120253-0766667cb4d1 // indirect
deps: Update aws-sdk-go-based to 0.6.0
2020-08-18 18:49:31 +02:00
github.com/hashicorp/aws-sdk-go-base v0.6.0
Update the Consul API client Some users would want to use Consul namespaces when using the Consul backend but the version of the Consul API client we use is too old and don't support them. In preparation for this change this patch just update it the client and replace testutil.NewTestServerConfig() by testutil.NewTestServerConfigT() in the tests.
2021-07-14 14:42:45 +02:00
github.com/hashicorp/consul/api v1.9.1
Merge remote-tracking branch 'origin/main' into update-consul
2021-07-28 12:18:01 +02:00
github.com/hashicorp/consul/sdk v0.8.0
dependencies: updating Azure Dependencies * github.com/Azure/azure-sdk-for-go to v47.1.0 * github.com/Azure/go-autorest to v0.11.10 * github.com/hashicorp/go-azure-helpers to v0.13.0 * github.com/tombuildsstuff/giovanni to v0.14.0
2020-10-27 19:06:17 +01:00
github.com/hashicorp/errwrap v1.1.0
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/hashicorp/go-azure-helpers v0.14.0
vendor: github.com/hashicorp/go-checkpoint@v0.5.0 go get github.com/hashicorp/go-checkpoint@v0.5.0 go mod tidy go mod vendor
2019-02-21 09:50:02 +01:00
github.com/hashicorp/go-checkpoint v0.5.0
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/hashicorp/go-cleanhttp v0.5.1
bump go-getter to 1.5.2 (#28189)
2021-04-05 15:01:47 +02:00
github.com/hashicorp/go-getter v1.5.2
update go-plugin and go-hclog
2020-11-06 22:38:26 +01:00
github.com/hashicorp/go-hclog v0.15.0
vendor: go get github.com/hashicorp/go-msgpack@v0.5.4 By upgrading this to a version that supports Go Modules, we can avoid the redundant dependencies labix.org/v2/mgo and launchpad.net/gocheck. These dependencies come via hashicorp/consul, which we have vendored for the Consul backend. There are no changes to the go-msgpack code here; we're just adopting a newer version that has a go.mod present so that its dependencies can be determined more accurately.
2019-04-24 03:05:41 +02:00
github.com/hashicorp/go-msgpack v0.5.4 // indirect
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/hashicorp/go-multierror v1.1.1
deps: update go-plugin to v1.4.1 (#28465) + go mod tidy
2021-04-21 17:41:22 +02:00
github.com/hashicorp/go-plugin v1.4.1
gomod: update `go-tfe`
2019-04-08 11:13:14 +02:00
github.com/hashicorp/go-retryablehttp v0.5.2
go get go-tfe@v0.15.0
2021-05-14 03:29:18 +02:00
github.com/hashicorp/go-tfe v0.15.0
gomod: update `go-tfe`
2019-04-08 11:13:14 +02:00
github.com/hashicorp/go-uuid v1.0.1
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/hashicorp/go-version v1.2.1
configs/configupgrade: do not panic on HEREDOCs. (#20281) Previously, configupgrade would panic if it encountered a HEREDOC. For the time being, we will simply print out the HEREDOC as-is. Unfortunately, we discovered that terraform 0.11's version of HCL allowed for HEREDOCs with the termination delimiter inline (instead of on a newline, which is technically correct). Since 0.12configupgrade needs to be bug-compatible with terraform 0.11, we must roll back to the same version of HCL used in terraform 0.11.
2019-02-09 00:51:53 +01:00
github.com/hashicorp/hcl v0.0.0-20170504190234-a4b07c25de5f
update hcl v2.10.1
2021-07-21 14:59:37 +02:00
github.com/hashicorp/hcl/v2 v2.10.1
update hcl and terraform-config-inspect
2021-02-09 14:37:59 +01:00
github.com/hashicorp/terraform-config-inspect v0.0.0-20210209133302-4fd17a0faac2
Include scopes in login URL
2020-09-14 18:21:20 +02:00
github.com/hashicorp/terraform-svchost v0.0.0-20200729002733-f050f53b9734
Add kubernetes backend Co-authored-by: Dan Ramich <danold215@gmail.com>
2020-04-13 22:17:17 +02:00
github.com/hashicorp/yamux v0.0.0-20181012175058-2f1d1f20f75d // indirect
deps: Bump github.com/aws/aws-sdk-go@v1.37.0 Changes: ``` * backend/s3: Support for AWS Single-Sign On (SSO) cached credentials ``` Updated via: ``` go get github.com/aws/aws-sdk-go@v1.37.0 go mod tidy ``` Please note that Terraform CLI will not initiate or perform the AWS SSO login flow. It is expected that you have already performed the SSO login flow using AWS CLI using the `aws sso login` command, or by some other mechanism before executing Terraform. More precisely, this credential handling must find a valid non-expired access token for the AWS SSO user portal URL in `~/.aws/sso/cache`. If a cached token is not found, is expired, or the file is malformed an error will be returned. You can use configure AWS SSO credentials from the AWS shared configuration file by specifying the required keys in the profile: ``` sso_account_id sso_region sso_role_name sso_start_url ``` For example, the following defines a profile "devsso" and specifies the AWS SSO parameters that defines the target account, role, sign-on portal, and the region where the user portal is located. Note: all SSO arguments must be provided, or an error will be returned. ``` [profile devsso] sso_start_url = https:my-sso-portal.awsapps.com/start sso_role_name = SSOReadOnlyRole sso_region = us-east-1 sso_account_id = 123456789012 ``` Additional Resources * [Configuring the AWS CLI to use AWS Single Sign-On](https:docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html) * [AWS Single Sign-On User Guide](https:docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html)
2021-01-28 21:22:01 +01:00
github.com/jmespath/go-jmespath v0.4.0
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-25 01:13:05 +02:00
github.com/joyent/triton-go v0.0.0-20180313100802-d8f9c0314926
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/jtolds/gls v4.2.1+incompatible // indirect
vendor: github.com/kardianos/osext@2bc1f35cddc0
2019-02-22 23:16:33 +01:00
github.com/kardianos/osext v0.0.0-20190222173326-2bc1f35cddc0
Update libpq This is needed to make it possible to use the scram-sha-256 authentication method for the pg backend. It's not easy to write unit-tests for this since it requires a specific configuration of the PostgreSQL server, I did test it manually thought and everything seems to work like it should. Closes https://github.com/hashicorp/terraform/issues/24016
2020-11-11 22:31:24 +01:00
github.com/lib/pq v1.8.0
backend/cos: Add TencentCloud backend cos with lock (#22540) * add TencentCloud COS backend for remote state * add vendor of dependence * fixed error not handle and remove default value for prefix argument * get appid from TF_COS_APPID environment variables
2020-02-13 17:37:11 +01:00
github.com/likexian/gokit v0.20.15
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-25 01:13:05 +02:00
github.com/lusis/go-artifactory v0.0.0-20160115162124-7e4ce345df82
communicator/winrm: include configured timeout in winrm server * upgrade windows dependencies * communicator/winrm: include configured timeout in winrm server
2020-06-25 14:41:09 +02:00
github.com/masterzen/simplexml v0.0.0-20190410153822-31eea3082786 // indirect
github.com/masterzen/winrm v0.0.0-20200615185753-c42b5136ff88
go get github.com/mattn/go-colorable@v0.1.8
2020-10-14 19:46:54 +02:00
github.com/mattn/go-isatty v0.0.12
vendor: github.com/mattn/go-shellwords@v1.0.4
2019-02-22 17:54:29 +01:00
github.com/mattn/go-shellwords v1.0.4
update mitchellh/cli
2020-11-30 18:13:02 +01:00
github.com/mitchellh/cli v1.1.2
vendor: github.com/mitchellh/colorstring@d06e56a500db go get github.com/mitchellh/colorstring@d06e56a500db go mod tidy go mod vendor
2019-02-21 09:57:51 +01:00
github.com/mitchellh/colorstring v0.0.0-20190213212951-d06e56a500db
vendor: go get github.com/mitchellh/copystructure@v1.0.0
2019-02-12 13:06:10 +01:00
github.com/mitchellh/copystructure v1.0.0
modules: update Azure deps to latest The dependencies here are dated and are causing conflicts with the ACME provider, namely the version of the top-level autorest package. This explicitly updates the Azure SDK and autorest packages, with the separately versioned sub-packages being added automatically.
2019-07-30 00:19:40 +02:00
github.com/mitchellh/go-homedir v1.1.0
vendor: github.com/mitchellh/go-linereader@1b945b3263eb go get github.com/mitchellh/go-linereader@1b945b3263eb go mod tidy go mod vendor
2019-02-21 09:59:37 +01:00
github.com/mitchellh/go-linereader v0.0.0-20190213213312-1b945b3263eb
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
github.com/mitchellh/go-wordwrap v1.0.0
adding gox to tools package
2020-06-17 16:47:53 +02:00
github.com/mitchellh/gox v1.0.1
vendor: github.com/hashicorp/hil@latest
2019-02-12 13:09:17 +01:00
github.com/mitchellh/mapstructure v1.1.2
vendor: go get github.com/mitchellh/panicwrap@v1.0.0
2019-11-05 10:22:11 +01:00
github.com/mitchellh/panicwrap v1.0.0
Add kubernetes backend Co-authored-by: Dan Ramich <danold215@gmail.com>
2020-04-13 22:17:17 +02:00
github.com/mitchellh/reflectwalk v1.0.1
communicator/winrm: include configured timeout in winrm server * upgrade windows dependencies * communicator/winrm: include configured timeout in winrm server
2020-06-25 14:41:09 +02:00
github.com/nu7hatch/gouuid v0.0.0-20131221200532-179d4d0c4d8d // indirect
github.com/packer-community/winrmcp v0.0.0-20180921211025-c76d91c1e7db
command: Revert local patch for pkg/browser The upstream bug with opening a browser on Windows Subsystem for Linux has been fixed, so this reverts our local patch for this. The approach upstream adds fallback support for x-www-browser and www-browser if xdg-open fails, and this fixes the problem on WSL. This reverts commit 12e090ce48f17e970cd7ba5de129f638ae296303.
2020-12-10 15:25:09 +01:00
github.com/pkg/browser v0.0.0-20201207095918-0426ae3fba23
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
github.com/pkg/errors v0.9.1
Update the Consul API client Some users would want to use Consul namespaces when using the Consul backend but the version of the Consul API client we use is too old and don't support them. In preparation for this change this patch just update it the client and replace testutil.NewTestServerConfig() by testutil.NewTestServerConfigT() in the tests.
2021-07-14 14:42:45 +02:00
github.com/posener/complete v1.2.3
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/smartystreets/assertions v0.0.0-20180927180507-b2de0cb4f26d // indirect
github.com/smartystreets/goconvey v0.0.0-20180222194500-ef6db91d284a // indirect
Add kubernetes backend Co-authored-by: Dan Ramich <danold215@gmail.com>
2020-04-13 22:17:17 +02:00
github.com/spf13/afero v1.2.2
backend/cos: Add TencentCloud backend cos with lock (#22540) * add TencentCloud COS backend for remote state * add vendor of dependence * fixed error not handle and remove default value for prefix argument * get appid from TF_COS_APPID environment variables
2020-02-13 17:37:11 +01:00
github.com/tencentcloud/tencentcloud-sdk-go v3.0.82+incompatible
github.com/tencentyun/cos-go-sdk-v5 v0.0.0-20190808065407-f07404cefc8c
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
github.com/tombuildsstuff/giovanni v0.15.1
vendor: github.com/xanzy/ssh-agent@v0.2.1
2019-02-22 15:22:13 +01:00
github.com/xanzy/ssh-agent v0.2.1
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-25 01:13:05 +02:00
github.com/xlab/treeprint v0.0.0-20161029104018-1d6e34225557
update go-cty to v1.9.0
2021-07-07 16:07:42 +02:00
github.com/zclconf/go-cty v1.9.0
internal/moduletest: Experimental module testing helpers As part of ongoing research into Terraform testing we'd like to use an experimental feature to validate our current understanding that expressing tests as part of the Terraform language, as opposed to in some other language run alongside, is a good and viable way to write practical module integration tests. This initial experimental incarnation of that idea is implemented as a provider, just because that's an easier extension point for research purposes than a first-class language feature would be. Whether this would ultimately emerge as a provider similar to this or as custom language constructs will be a matter for future research, if this first experiment confirms that tests written in the Terraform language are the best direction to take. The previous incarnation of this experiment was an externally-developed provider apparentlymart/testing, listed on the Terraform Registry. That helped with showing that there are some useful tests that we can write in the Terraform language, but integrating such a provider into Terraform will allow us to make use of it in the also-experimental "terraform test" command, which will follow in subsequent commits, to see how this might fit into a development workflow.
2021-02-05 01:08:51 +01:00
github.com/zclconf/go-cty-debug v0.0.0-20191215020915-b22d67c1ba0b
vendor: go get github.com/zclconf/go-cty-yaml@v1.0.2
2020-06-17 19:05:08 +02:00
github.com/zclconf/go-cty-yaml v1.0.2
go.mod,backend: update coreos/etcd dependency to release-3.4 branch etcd rewrote its import path from coreos/etcd to go.etcd.io/etcd. Changed the imports path in this commit, which also updates the code version. This lets us remove the github.com/ugorji/go/codec dependency, which was pinned to a fairly old version. The net change is a loss of 30,000 lines of code in the vendor directory. (I first noticed this problem because the outdated go/codec dependency was causing a dependency failure when I tried to put Terraform and another project in the same vendor directory.) Note the version shows up funkily in go.mod, but I verified visually it's the same commit as the "release-3.4" tag in github.com/coreos/etcd. The etcd team plans to fix the release version tagging in v3.5, which should be released soon.
2021-01-27 23:04:52 +01:00
go.etcd.io/etcd v0.5.0-alpha.5.0.20210428180535-15715dcf1ace
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
golang.org/x/crypto v0.0.0-20210322153248-0c34fe9e7dc2
add impersonation
2021-04-07 00:58:24 +02:00
golang.org/x/mod v0.4.2
dependencies: upgrade all the azure things
2021-03-22 17:22:16 +01:00
golang.org/x/net v0.0.0-20210226172049-e18ecbb05110
add impersonation
2021-04-07 00:58:24 +02:00
golang.org/x/oauth2 v0.0.0-20210313182246-cd4f82c27b84
golang.org/x/sys v0.0.0-20210403161142-5e06dd20ab57
internal/terminal: Interrogate and initialize the terminal, if any This is a helper package that creates a very thin abstraction over terminal setup, with the main goal being to deal with all of the extra setup we need to do in order to get a UTF-8-supporting virtual terminal on a Windows system.
2021-01-12 03:13:21 +01:00
golang.org/x/term v0.0.0-20201210144234-2321bbc49cbf
config: Use Unicode 13 rules for string manipulation Although we don't typically do configuration-level string wrangling directly in Terraform, we delegate to several other upstream libraries that do. These upgrades all switch to newer versions that support the latest definitions from Unicode 13, primarily affecting operations such as converting strings to upper/lowercase or splitting strings into component characters (substr, reverse, etc). The tests for the upstream libraries didn't show any regressions from these updates, so the Unicode 13 changes seem to be backward-compatible additions rather than significant breaking changes. (Our go.mod file had also become non-canonical in some ways, and the Go toolchain fixed that as part of this work, causing a few extra style-only diffs here that shouldn't cause any change in behavior.)
2021-02-23 18:18:29 +01:00
golang.org/x/text v0.3.5
add impersonation
2021-04-07 00:58:24 +02:00
golang.org/x/tools v0.1.0
google.golang.org/api v0.44.0-impersonate-preview
google.golang.org/grpc v1.36.0
update proto packages
2020-12-01 20:04:17 +01:00
google.golang.org/protobuf v1.25.0
udpate lost go.mod entry go.sum and vendor are OK
2019-06-10 22:15:54 +02:00
gopkg.in/ini.v1 v1.42.0 // indirect
Add kubernetes backend Co-authored-by: Dan Ramich <danold215@gmail.com>
2020-04-13 22:17:17 +02:00
k8s.io/api v0.0.0-20190620084959-7cf5895f2711
k8s.io/apimachinery v0.0.0-20190913080033-27d36303b655
k8s.io/client-go v10.0.0+incompatible
k8s.io/utils v0.0.0-20200411171748-3d5a2fe318e4
)
tweak go.mod replaces
2021-04-16 17:12:04 +02:00
replace google.golang.org/grpc v1.36.0 => google.golang.org/grpc v1.27.1
go get go-tfe@v0.15.0
2021-05-14 03:29:18 +02:00
replace gomod
2021-04-26 15:34:11 +02:00
replace github.com/golang/mock v1.5.0 => github.com/golang/mock v1.4.4
config: Use Unicode 13 rules for string manipulation Although we don't typically do configuration-level string wrangling directly in Terraform, we delegate to several other upstream libraries that do. These upgrades all switch to newer versions that support the latest definitions from Unicode 13, primarily affecting operations such as converting strings to upper/lowercase or splitting strings into component characters (substr, reverse, etc). The tests for the upstream libraries didn't show any regressions from these updates, so the Unicode 13 changes seem to be backward-compatible additions rather than significant breaking changes. (Our go.mod file had also become non-canonical in some ways, and the Go toolchain fixed that as part of this work, causing a few extra style-only diffs here that shouldn't cause any change in behavior.)
2021-02-23 18:18:29 +01:00
dependencies: updating Azure/azure-sdk-for-go, Azure/go-autorest, hashicorp/go-azure-helpers, tombuildsstuff/giovanni * updating `github.com/Azure/azure-sdk-for-go` to `v45.0.0` * updating `github.com/Azure/go-autorest` to `v0.11.3` * updating `github.com/hashicorp/go-azure-helpers` to `v0.12.0` * updating `github.com/tombuildsstuff/giovanni` to `v0.12.0`
2020-08-07 10:45:40 +02:00
replace k8s.io/client-go => k8s.io/client-go v0.0.0-20190620085101-78d2af792bab
deps: github.com/hashicorp/aws-sdk-go-base@v0.4.0 (#22994)
2019-10-11 18:50:12 +02:00
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
go 1.14