net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839

mattrobenolt · 2022-05-10T22:47:38Z

What version of Go are you using (`go version`)?

$ go version
go version go1.18 darwin/amd64

This is also reproduced against go1.17.8, so doesn't appear to be new to go1.18.

Does this issue reproduce with the latest release?

Yes.

What operating system and processor architecture are you using (`go env`)?

macOS 12.3, Intel (amd64)

go env Output

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/xxx/Library/Caches/go-build"
GOENV="/Users/xxx/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/xxx/go/pkg/mod"
GOOS="darwin"
GOPATH="/Users/xxx/go"
GOPROXY="https://proxy.golang.org/,direct"
GOROOT="/usr/local/Cellar/go/1.18/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.18/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/pb/fk1_tmbn1nq32bgpd6njflcw0000gn/T/go-build3259567292=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Making a DNS lookup against an ipv6 link-local address hangs and fails on macOS when using thenative (non-CGO) resolver.

This appears to manifest within the non-CGO based DNS resolver, but I believe it's more generally applicable to the network stack itself, it's just easier to reproduce through DNS.

The simplest reproduction we could come up with was this compiled with CGO_ENABLED=0:

package main

import (
	"context"
	"fmt"
	"net"
	"os"
	"time"
)

func main() {
	ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second)
	defer cancel()
	ips, err := net.DefaultResolver.LookupIP(ctx, "ip", "google.com")
	if err != nil {
		fmt.Fprintf(os.Stderr, "Could not get IPs: %v\n", err)
		os.Exit(1)
	}
	for _, ip := range ips {
		fmt.Printf("google.com. IN A %s\n", ip.String())
	}
}

Paired with an /etc/resolv.conf of:

nameserver fe80::a04e:cfff:fe2f:ad64%en0
nameserver 10.0.0.1

I've deduced this down to explicitly any link-local address (fe80::*) and not generically to ipv6. Other ipv6 addresses, both public and private network appear fine.

This behavior is especially concerning because it seems to cascade into larger macOS failures. All DNS seems to start failing on the whole system requiring ultimately a reboot to restore stability.

Given this, I believe this is also a bug within macOS that Go happens to be exploiting somehow.

I personally don't have a macOS machine to iterate on this, but we've deduced this both with customers running our CLI (https://github.com/planetscale/cli) as well as employees internally.

After a bunch of deducing, we've narrowed it down to the link-local address.

Again, when compiled with CGO_ENABLED=1, everything works correctly and is fine. The issue only occurs when compiled with CGO_ENABLED=0, triggering the pure Go DNS resolution path.

We originally thought this was related to arm64 (M1 Macs), but was able to finally reproduce it on Intel.

What did you expect to see?

Fast DNS resolution

What did you see instead?

Program hangs, eventually times out, in extreme cases, causing entire OS to become unstable.

For additional context: planetscale/discussion#181

The text was updated successfully, but these errors were encountered:

heschi · 2022-05-11T19:04:39Z

cc @ianlancetaylor @neild

dannyfallon · 2022-08-11T09:59:10Z

We reproduced this with Go 1.18.4 and Go 1.16.5 on M1 and Intel machines running OS X 12.3-12.5 with two different Go applications. All affected users had the fe80::* IPv6 DNS address in their nameservers. The behaviour was always what the OP described as the extreme circumstances - hung process that ignores signals, eventual network disconnection and then a frozen machine needing forced reboots.

Changing DNS servers on the network connection to drop the fe80::* address resolved it. As a mitigation we also started to build OS X binaries on OS X machines with Cgo enabled to force the use of the Cgo resolver. We lost several days debugging this ourselves and when I came to report this I found this issue already. Is there any update or ETA on when investigation might take place? This seems fairly critical.

apparentlymart · 2022-09-06T16:51:39Z

One possible way to confound a reproduction on darwin_amd64 is if a program is being built for both darwin_amd64 and darwin_arm64 on a build worker whose native toolchain is the darwin_arm64 one. In that situation the default for CGO_ENABLED is different between the two targets: darwin_arm64 is considered to be a cross-compile and therefore CGO_ENABLED defaults to off.

I wrote some more about this in a comment on the general issue about the pure Go resolver on macOS. The short version is that if you want to reproduce it reliably it's important to explicitly set CGO_ENABLED=0 or CGO_ENABLED=1 consistently across builds for both architectures, and not rely on the default. That will then ensure that both of your builds are using the same resolver implementation.

silvestriluca · 2022-09-13T10:05:49Z

I'm experiencing this issue too using Terraform (which is based on GoLang).
Very very bad bug. All my network stack crashes and I'm forced to:

force close the apps that are using nework (slack, browser, terminal...)
Reboot mac

Check hashicorp/terraform#31467 (comment)

It is worth to get in touch with macOS network devs, because even if there is some issue in go implementation, network stack shouldn't crash so dramatically, to the point that reboot is the only option.

heschi · 2022-09-13T16:57:11Z

cc @golang/darwin

…config see this issue golang/go#52839 Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [hashicorp/terraform](https://togithub.com/hashicorp/terraform) | major | `0.15.5` -> `1.3.5` | --- ### Release Notes <details> <summary>hashicorp/terraform</summary> ### [`v1.3.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.4...v1.3.5) #### 1.3.5 (November 17, 2022) BUG FIXES: - Prevent crash while serializing the plan for an empty destroy operation ([#32207](https://togithub.com/hashicorp/terraform/issues/32207)) - Allow a destroy plan to refresh instances while taking into account that some may no longer exist ([#32208](https://togithub.com/hashicorp/terraform/issues/32208)) - Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix inconsistent behaviour in empty vs null collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Prevent file uploads from creating unneeded temporary files when the payload size is known ([#32206](https://togithub.com/hashicorp/terraform/issues/32206)) - Nested attributes marked sensitive by schema no longer reveal sub-attributes in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Nested attributes now more consistently display when they become unknown or null values in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Sensitive values are now always displayed as `(sensitive value)` instead of sometimes as `(sensitive)` \[GH32004] ### [`v1.3.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.3...v1.3.4) ##### 1.3.4 (November 02, 2022) BUG FIXES: - Fix invalid refresh-only plan caused by data sources being deferred to apply ([#32111](https://togithub.com/hashicorp/terraform/issues/32111)) - Optimize the handling of condition checks during apply to prevent performance regressions with large numbers of instances ([#32123](https://togithub.com/hashicorp/terraform/issues/32123)) - Output preconditions should not be evaluated during destroy ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Fix crash from `console` when outputs contain preconditions ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Destroy with no state would still attempt to evaluate some values ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Prevent unnecessary evaluation and planning of resources during the pre-destroy refresh ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - AzureRM Backend: support for generic OIDC authentication via the `oidc_token` and `oidc_token_file_path` properties ([#31966](https://togithub.com/hashicorp/terraform/issues/31966)) - Input and Module Variables: Convert variable types before attempting to apply default values. ([#32027](https://togithub.com/hashicorp/terraform/issues/32027)) - When installing remote module packages delivered in tar format, Terraform now limits the tar header block size to 1MiB to avoid unbounded memory usage for maliciously-crafted module packages. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform will now reject excessively-complex regular expression patterns passed to the `regex`, `regexall`, and `replace` functions, to avoid unbounded memory usage for maliciously-crafted patterns. This change should not affect any reasonable patterns intended for practical use. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform on Windows now rejects invalid environment variables whose values contain the NUL character when propagating environment variables to a child process such as a provider plugin. Previously Terraform would incorrectly treat that character as a separator between two separate environment variables. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) ### [`v1.3.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.2...v1.3.3) ##### 1.3.3 (October 19, 2022) BUG FIXES: - Fix error when removing a resource from configuration which has according to the provider has already been deleted. ([#31850](https://togithub.com/hashicorp/terraform/issues/31850)) - Fix error when setting empty collections into variables with collections of nested objects with default values. ([#32033](https://togithub.com/hashicorp/terraform/issues/32033)) ### [`v1.3.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.1...v1.3.2) #### 1.3.2 (October 06, 2022) BUG FIXES: - Fixed a crash caused by Terraform incorrectly re-registering output value preconditions during the apply phase (rather than just reusing the already-planned checks from the plan phase). ([#31890](https://togithub.com/hashicorp/terraform/issues/31890)) - Prevent errors when the provider reports that a deposed instance no longer exists ([#31902](https://togithub.com/hashicorp/terraform/issues/31902)) - Using `ignore_changes = all` could cause persistent diffs with legacy providers ([#31914](https://togithub.com/hashicorp/terraform/issues/31914)) - Fix cycles when resource dependencies cross over between independent provider configurations ([#31917](https://togithub.com/hashicorp/terraform/issues/31917)) - Improve handling of missing resource instances during `import` ([#31878](https://togithub.com/hashicorp/terraform/issues/31878)) ### [`v1.3.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.0...v1.3.1) #### 1.3.1 (September 28, 2022) NOTE: - On `darwin/amd64` and `darwin/arm64` architectures, `terraform` binaries are now built with CGO enabled. This should not have any user-facing impact, except in cases where the pure Go DNS resolver causes problems on recent versions of macOS: using CGO may mitigate these issues. Please see the upstream bug [https://github.com/golang/go/issues/52839](https://togithub.com/golang/go/issues/52839) for more details. BUG FIXES: - Fixed a crash when using objects with optional attributes and default values in collections, most visible with nested modules. ([#31847](https://togithub.com/hashicorp/terraform/issues/31847)) - Prevent cycles in some situations where a provider depends on resources in the configuration which are participating in planned changes. ([#31857](https://togithub.com/hashicorp/terraform/issues/31857)) - Fixed an error when attempting to destroy a configuration where resources do not exist in the state. ([#31858](https://togithub.com/hashicorp/terraform/issues/31858)) - Data sources which cannot be read during will no longer prevent the state from being serialized. ([#31871](https://togithub.com/hashicorp/terraform/issues/31871)) - Fixed a crash which occured when a resource with a precondition and/or a postcondition appeared inside a module with two or more instances. ([#31860](https://togithub.com/hashicorp/terraform/issues/31860)) ### [`v1.3.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.9...v1.3.0) #### 1.3.0 (September 21, 2022) NEW FEATURES: - **Optional attributes for object type constraints:** When declaring an input variable whose type constraint includes an object type, you can now declare individual attributes as optional, and specify a default value to use if the caller doesn't set it. For example: ```terraform variable "with_optional_attribute" { type = object({ a = string # a required attribute b = optional(string) # an optional attribute c = optional(number, 127) # an optional attribute with a default value }) } ``` Assigning `{ a = "foo" }` to this variable will result in the value `{ a = "foo", b = null, c = 127 }`. - Added functions: `startswith` and `endswith` allow you to check whether a given string has a specified prefix or suffix. ([#31220](https://togithub.com/hashicorp/terraform/issues/31220)) UPGRADE NOTES: - `terraform show -json`: Output changes now include more detail about the unknown-ness of the planned value. Previously, a planned output would be marked as either fully known or partially unknown, with the `after_unknown` field having value `false` or `true` respectively. Now outputs correctly expose the full structure of unknownness for complex values, allowing consumers of the JSON output format to determine which values in a collection are known only after apply. - `terraform import`: The `-allow-missing-config` has been removed, and at least an empty configuration block must exist to import a resource. - Consumers of the JSON output format expecting on the `after_unknown` field to be only `false` or `true` should be updated to support [the change representation](https://www.terraform.io/internals/json-format#change-representation) described in the documentation, and as was already used for resource changes. ([#31235](https://togithub.com/hashicorp/terraform/issues/31235)) - AzureRM Backend: This release concludes [the deprecation cycle started in Terraform v1.1](https://www.terraform.io/language/upgrade-guides/1-1#preparation-for-removing-azure-ad-graph-support-in-the-azurerm-backend) for the `azurerm` backend's support of "ADAL" authentication. This backend now supports only "MSAL" (Microsoft Graph) authentication. This follows from [Microsoft's own deprecation of Azure AD Graph](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq), and so you must follow the migration instructions presented in that Azure documentation to adopt Microsoft Graph and then change your backend configuration to use MSAL authentication before upgrading to Terraform v1.3. - When making requests to HTTPS servers, Terraform will now reject invalid handshakes that have duplicate extensions, as required by RFC 5246 section 7.4.1.4 and RFC 8446 section 4.2. This may cause new errors when interacting with existing buggy or misconfigured TLS servers, but should not affect correct servers. This only applies to requests made directly by Terraform CLI, such as provider installation and remote state storage. Terraform providers are separate programs which decide their own policy for handling of TLS handshakes. - The following backends, which were deprecated in v1.2.3, have now been removed: `artifactory`, `etcd`, `etcdv3`, `manta`, `swift`. The legacy backend name `azure` has also been removed, because the current Azure backend is named `azurerm`. ([#31711](https://togithub.com/hashicorp/terraform/issues/31711)) ENHANCEMENTS: - config: Optional attributes for object type constraints, as described under new features above. ([#31154](https://togithub.com/hashicorp/terraform/issues/31154)) - config: New built-in function `timecmp` allows determining the ordering relationship between two timestamps while taking potentially-different UTC offsets into account. ([#31687](https://togithub.com/hashicorp/terraform/pull/31687)) - config: When reporting an error message related to a function call, Terraform will now include contextual information about the signature of the function that was being called, as an aid to understanding why the call might have failed. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: When reporting an error or warning message that isn't caused by values being unknown or marked as sensitive, Terraform will no longer mention any values having those characteristics in the contextual information presented alongside the error. Terraform will still return this information for the small subset of error messages that are specifically about unknown values or sensitive values being invalid in certain contexts. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: `moved` blocks can now describe resources moving to and from modules in separate module packages. ([#31556](https://togithub.com/hashicorp/terraform/issues/31556)) - `terraform fmt` now accepts multiple target paths, allowing formatting of several individual files at once. ([#31687](https://togithub.com/hashicorp/terraform/issues/31687)) - `terraform init`: provider installation errors now mention which host Terraform was downloading from ([#31524](https://togithub.com/hashicorp/terraform/issues/31524)) - CLI: Terraform will report more explicitly when it is proposing to delete an object due to it having moved to a resource instance that is not currently declared in the configuration. ([#31695](https://togithub.com/hashicorp/terraform/issues/31695)) - CLI: When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about pre-plan run tasks ([#31617](https://togithub.com/hashicorp/terraform/issues/31617)) - The AzureRM Backend now only supports MSAL (and Microsoft Graph) and no longer makes use of ADAL (and Azure Active Directory Graph) for authentication ([#31070](https://togithub.com/hashicorp/terraform/issues/31070)) - The COS backend now supports global acceleration. ([#31425](https://togithub.com/hashicorp/terraform/issues/31425)) - provider plugin protocol: The Terraform CLI now calls `PlanResourceChange` for compatible providers when destroying resource instances. ([#31179](https://togithub.com/hashicorp/terraform/issues/31179)) - As an implementation detail of the Terraform Cloud integration, Terraform CLI will now capture and upload [the JSON integration format for state](https://www.terraform.io/internals/json-format#state-representation) along with any newly-recorded state snapshots, which then in turn allows Terraform Cloud to provide that information to API-based external integrations. ([#31698](https://togithub.com/hashicorp/terraform/issues/31698)) BUG FIXES: - config: Terraform was not previously evaluating preconditions and postconditions during the apply phase for resource instances that didn't have any changes pending, which was incorrect because the outcome of a condition can potentially be affected by changes to *other* objects in the configuration. Terraform will now always check the conditions for every resource instance included in a plan during the apply phase, even for resource instances that have "no-op" changes. This means that some failures that would previously have been detected only by a subsequent run will now be detected during the same run that caused them, thereby giving the feedback at the appropriate time. ([#31491](https://togithub.com/hashicorp/terraform/issues/31491)) - `terraform show -json`: Fixed missing markers for unknown values in the encoding of partially unknown tuples and sets. ([#31236](https://togithub.com/hashicorp/terraform/issues/31236)) - `terraform output` CLI help documentation is now more consistent with web-based documentation. ([#29354](https://togithub.com/hashicorp/terraform/issues/29354)) - `terraform init`: Error messages now handle the situation where the underlying HTTP client library does not indicate a hostname for a failed request. ([#31542](https://togithub.com/hashicorp/terraform/issues/31542)) - `terraform init`: Don't panic if a child module contains a resource with a syntactically-invalid resource type name. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - CLI: The representation of destroying already-`null` output values in a destroy plan will no longer report them as being deleted, which avoids reporting the deletion of an output value that was already absent. ([#31471](https://togithub.com/hashicorp/terraform/issues/31471)) - `terraform import`: Better handling of resources or modules that use `for_each`, and situations where data resources are needed to complete the operation. ([#31283](https://togithub.com/hashicorp/terraform/issues/31283)) EXPERIMENTS: - This release concludes the `module_variable_optional_attrs` experiment, which started in Terraform v0.14.0. The final design of the optional attributes feature is similar to the experimental form in the previous releases, but with two major differences: - The `optional` function-like modifier for declaring an optional attribute now accepts an optional second argument for specifying a default value to use when the attribute isn't set by the caller. If not specified, the default value is a null value of the appropriate type as before. - The built-in `defaults` function, previously used to meet the use-case of replacing null values with default values, will not graduate to stable and has been removed. Use the second argument of `optional` inline in your type constraint to declare default values instead. If you have any experimental modules that were participating in this experiment, you will need to remove the experiment opt-in and adopt the new syntax for declaring default values in order to migrate your existing module to the stablized version of this feature. If you are writing a shared module for others to use, we recommend declaring that your module requires Terraform v1.3.0 or later to give specific feedback when using the new feature on older Terraform versions, in place of the previous declaration to use the experimental form of this feature: ```hcl terraform { required_version = ">= 1.3.0" } ``` ### [`v1.2.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.8...v1.2.9) #### 1.2.9 (September 07, 2022) ENHANCEMENTS: - terraform init: add link to documentation when a checksum is missing from the lock file. ([#31726](https://togithub.com/hashicorp/terraform/issues/31726)) ### [`v1.2.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.7...v1.2.8) ##### 1.2.8 (August 24, 2022) BUG FIXES: - config: The `flatten` function will no longer panic if given a null value that has been explicitly converted to or implicitly inferred as having a list, set, or tuple type. Previously Terraform would panic in such a situation because it tried to "flatten" the contents of the null value into the result, which is impossible. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) - config: The `tolist`, `toset`, and `tomap` functions, and various automatic conversions that include similar logic, will no longer panic when asked to infer an element type that is convertable from both a tuple type and a list type whose element type is not yet known. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) ### [`v1.2.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.6...v1.2.7) #### 1.2.7 (August 10, 2022) ENHANCEMENTS: - config: Check for direct references to deprecated computed attributes. ([#31576](https://togithub.com/hashicorp/terraform/issues/31576)) BUG FIXES: - config: Fix an crash if a submodule contains a resource whose implied provider local name contains invalid characters, by adding additional validation rules to turn it into a real error. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - core: Fix some handling of provider schema attributes which use the newer "structural typing" mechanism introduced with protocol version 6, and therefore with the new Terraform Plugin Framework ([#31532](https://togithub.com/hashicorp/terraform/issues/31532)) - command: Add missing output text for applyable refresh plans. ([#31469](https://togithub.com/hashicorp/terraform/issues/31469)) ### [`v1.2.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.5...v1.2.6) #### 1.2.6 (July 27, 2022) ENHANCEMENTS: - Add a warning and guidance when `terraform init` fails to fully populate the `.terraform.lock.hcl` file. ([#31399](https://togithub.com/hashicorp/terraform/issues/31399)) - Add a direct link to the relevant documentation when `terraform init` fails on missing checksums. ([#31408](https://togithub.com/hashicorp/terraform/issues/31408)) BUG FIXES: - Fix panic on `terraform show` when state file is invalid or unavailable. ([#31444](https://togithub.com/hashicorp/terraform/issues/31444)) - Fix `terraform providers lock` command failing on missing checksums. ([#31389](https://togithub.com/hashicorp/terraform/issues/31389)) - Some combinations of move block operations would be executed in the wrong order ([#31499](https://togithub.com/hashicorp/terraform/issues/31499)) - Don't attribute an error to the provider when a computed attribute is listed in `ignore_changes` ([#31509](https://togithub.com/hashicorp/terraform/issues/31509)) ### [`v1.2.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.4...v1.2.5) ##### 1.2.5 (July 13, 2022) BUG FIXES: - Report correct error message when a prerelease field is included in the `required_version` global constraint. ([#31331](https://togithub.com/hashicorp/terraform/issues/31331)) - Fix case when extra blank lines were inserted into the plan for unchanged blocks. ([#31330](https://togithub.com/hashicorp/terraform/issues/31330)) ### [`v1.2.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.3...v1.2.4) ##### 1.2.4 (June 29, 2022) ENHANCEMENTS: - Improved validation of `required_providers` to prevent single providers from being required with multiple names. ([#31218](https://togithub.com/hashicorp/terraform/issues/31218)) - Improved plan performance by optimizing `addrs.Module.String` for allocations. ([#31293](https://togithub.com/hashicorp/terraform/issues/31293)) BUG FIXES: - backend/http: Fixed bug where the HTTP backend would fail to retry acquiring the state lock and ignored the `-lock-timeout` flag. ([#31256](https://togithub.com/hashicorp/terraform/issues/31256)) - Fix crash if a `precondition` or `postcondition` block omitted the required `condition` argument. ([#31290](https://togithub.com/hashicorp/terraform/issues/31290)) ### [`v1.2.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.2...v1.2.3) ##### 1.2.3 (June 15, 2022) UPGRADE NOTES: - The following remote state backends are now marked as deprecated, and are planned to be removed in a future Terraform release. These backends have been unmaintained since before Terraform v1.0, and may contain known bugs, outdated packages, or security vulnerabilities. - artifactory - etcd - etcdv3 - manta - swift BUG FIXES: - Missing check for error diagnostics in GetProviderSchema could result in panic ([#31184](https://togithub.com/hashicorp/terraform/issues/31184)) - Module registries returning X-Terraform-Get locations with no URL would error with "no getter available for X-Terraform-Get source protocol" ([#31237](https://togithub.com/hashicorp/terraform/issues/31237)) - Fix crash from concurrent operation on shared set of resource instance dependencies ([#31246](https://togithub.com/hashicorp/terraform/issues/31246)) - backend/cos: `tencentcloud-terraform-lock` tag was not removed in all cases ([#31223](https://togithub.com/hashicorp/terraform/issues/31223)) ### [`v1.2.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.1...v1.2.2) ##### 1.2.2 (June 01, 2022) ENHANCEMENTS: - Invalid `-var` arguments with spaces between the name and value now have an improved error message ([#30985](https://togithub.com/hashicorp/terraform/issues/30985)) BUG FIXES: - Terraform now hides invalid input values for sensitive root module variables when generating error diagnostics ([#30552](https://togithub.com/hashicorp/terraform/issues/30552)) - Fixed crash on CLI autocomplete ([#31160](https://togithub.com/hashicorp/terraform/issues/31160)) - The "Configuration contains unknown values" error message now includes attribute paths ([#31111](https://togithub.com/hashicorp/terraform/issues/31111)) ### [`v1.2.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.0...v1.2.1) #### 1.2.1 (May 23, 2022) BUG FIXES: - SSH provisioner connections fail when using signed `ed25519` keys ([#31092](https://togithub.com/hashicorp/terraform/issues/31092)) - Crash with invalid module source ([#31060](https://togithub.com/hashicorp/terraform/issues/31060)) - Incorrect "Module is incompatible with count, for_each, and depends_on" error when a provider is nested within a module along with a sub-module using `count` or `for_each` ([#31091](https://togithub.com/hashicorp/terraform/issues/31091)) ### [`v1.2.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.9...v1.2.0) #### 1.2.0 (May 18, 2022) UPGRADE NOTES: - If you use the [third-party credentials helper plugin terraform-credentials-env](https://togithub.com/apparentlymart/terraform-credentials-env), you should disable it as part of upgrading to Terraform v1.2 because similar functionality is now built in to Terraform itself. The new behavior supports the same environment variable naming scheme but has a difference in priority order from the credentials helper: `TF_TOKEN_...` environment variables will now take priority over credentials blocks in CLI configuration and credentials stored automatically by terraform login, which is not true for credentials provided by any credentials helper plugin. If you see Terraform using different credentials after upgrading, check to make sure you do not specify credentials for the same host in multiple locations. If you use the credentials helper in conjunction with the [hashicorp/tfe](https://registry.terraform.io/providers/hashicorp/tfe) Terraform provider to manage Terraform Cloud or Terraform Enterprise objects with Terraform, you should also upgrade to version 0.31 of that provider, which added the corresponding built-in support for these environment variables. - The official Linux packages for the v1.2 series now require Linux kernel version 2.6.32 or later. - When making outgoing HTTPS or other TLS connections as a client, Terraform now requires the server to support TLS v1.2. TLS v1.0 and v1.1 are no longer supported. Any safely up-to-date server should support TLS 1.2, and mainstream web browsers have required it since 2020. - When making outgoing HTTPS or other TLS connections as a client, Terraform will no longer accept CA certificates signed using the SHA-1 hash function. Publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015. (Note: the changes to Terraform's requirements when interacting with TLS servers apply only to requests made by Terraform CLI itself, such as provider/module installation and state storage requests. Terraform provider plugins include their own TLS clients which may have different requirements, and may add new requirements in their own releases, independently of Terraform CLI changes.) NEW FEATURES: - `precondition` and `postcondition` check blocks for resources, data sources, and module output values: module authors can now document assumptions and assertions about configuration and state values. If these conditions are not met, Terraform will report a custom error message to the user and halt further execution. - `replace_triggered_by` is a new `lifecycle` argument for managed resources which triggers replacement of an object based on changes to an upstream dependency. - You can now specify credentials for [Terraform-native services](https://www.terraform.io/internals/remote-service-discovery) using an environment variable named as `TF_TOKEN_` followed by an encoded version of the hostname. For example, Terraform will use variable `TF_TOKEN_app_terraform_io` as a bearer token for requests to "app.terraform.io", for the Terraform Cloud integration and private registry requests. ENHANCEMENTS: - When showing a plan, Terraform CLI will now only show "Changes outside of Terraform" if they relate to resources and resource attributes that contributed to the changes Terraform is proposing to make. ([#30486](https://togithub.com/hashicorp/terraform/issues/30486)) - Error messages for preconditions, postconditions, and custom variable validations are now evaluated as expressions, allowing interpolation of relevant values into the output. ([#30613](https://togithub.com/hashicorp/terraform/issues/30613)) - When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about post-plan [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks). ([#30141](https://togithub.com/hashicorp/terraform/issues/30141)) - Terraform will now show a slightly different note in the plan output if a data resource read is deferred to the apply step due to it depending on a managed resource that has changes pending. ([#30971](https://togithub.com/hashicorp/terraform/issues/30971)) - The "Invalid for_each argument" error message for unknown maps/sets now includes an additional paragraph to try to help the user notice they can move apply-time values into the map *values* instead of the map *keys*, and thus avoid the problem without resorting to `-target`. ([#30327](https://togithub.com/hashicorp/terraform/issues/30327)) - There are some small improvements to the error and warning messages Terraform will emit in the case of invalid provider configuration passing between modules. There are no changes to which situations will produce errors and warnings, but the messages now include additional information intended to clarify what problem Terraform is describing and how to address it. ([#30639](https://togithub.com/hashicorp/terraform/issues/30639)) - The environment variables `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` now serve as fallbacks for the arguments of the same name inside a `cloud` block configuring integration with Terraform Cloud. - The environment variable `TF_WORKSPACE` will now additionally serve as an implicit configuration of a single selected workspace on Terraform Cloud if (and only if) the `cloud` block does not include an explicit workspaces configuration. - The AzureRM Backend now defaults to using MSAL (and Microsoft Graph) rather than ADAL (and Azure Active Directory Graph) for authentication. ([#30891](https://togithub.com/hashicorp/terraform/issues/30891)) - The AzureRM Backend now supports authenticating as a service principal using OpenID Connect. ([#30936](https://togithub.com/hashicorp/terraform/pull/30936)) - When running on macOS, Terraform will now use platform APIs to validate certificates presented by TLS (HTTPS) servers. This may change exactly which root certificates Terraform will accept as valid. ([#30768](https://togithub.com/hashicorp/terraform/issues/30768)) - Show remote host in error message for clarity when installation of provider fails ([#30810](https://togithub.com/hashicorp/terraform/issues/30810)) - Terraform now prints a warning when adding an attribute to `ignore_changes` that is managed only by the provider. Specifying non-configurable attributes in `ignore_changes` has no effect because `ignore_changes` tells Terraform to ignore future changes made in the configuration. ([#30517](https://togithub.com/hashicorp/terraform/issues/30517)) - `terraform show -json` now includes exact type information for output values. ([#30945](https://togithub.com/hashicorp/terraform/issues/30945)) - The `ssh` provisioner connection now supports SSH over HTTP proxy. ([#30274](https://togithub.com/hashicorp/terraform/pull/30274)) - - The SSH client for provisioners now supports newer key algorithms, allowing it to connect to servers running more recent versions of OpenSSH. ([#30962](https://togithub.com/hashicorp/terraform/issues/30962)) BUG FIXES: - Terraform now handles type constraints, nullability, and custom variable validation properly for root module variables. Previously there was an order of operations problem where the nullability and custom variable validation were checked too early, prior to dealing with the type constraints, and thus that logic could potentially "see" an incorrectly-typed value in spite of the type constraint, leading to incorrect errors. ([#29959](https://togithub.com/hashicorp/terraform/issues/29959)) - When reporting a type mismatch between the true and false results of a conditional expression when both results are of the same structural type kind (object/tuple, or a collection thereof), Terraform will no longer return a confusing message like "the types are object and object, respectively", and will instead attempt to explain how the two structural types differ. ([#30920](https://togithub.com/hashicorp/terraform/issues/30920)) - Applying the various type conversion functions like `tostring`, `tonumber`, etc to `null` will now return a null value of the intended type. For example, `tostring(null)` converts from a null value of an unknown type to a null value of string type. Terraform can often handle such conversions automatically when needed, but explicit annotations like this can help Terraform to understand author intent when inferring type conversions for complex-typed values. ([#30879](https://togithub.com/hashicorp/terraform/issues/30879)) - Terraform now returns an error when `cidrnetmask()` is called with an IPv6 address, as it was previously documented to do. IPv6 standards do not preserve the "netmask" syntax sometimes used for IPv4 network configuration; use CIDR prefix syntax instead. ([#30703](https://togithub.com/hashicorp/terraform/issues/30703)) - When performing advanced state management with the `terraform state` commands, Terraform now checks the `required_version` field in the configuration before proceeding. ([#30511](https://togithub.com/hashicorp/terraform/pull/30511)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will now prioritize local terraform variables over remote terraform variables in operations such as `import`, `plan`, `refresh` and `apply` for workspaces in local execution mode. This behavior applies to both `remote` backend and the `cloud` integration configuration. ([#29972](https://togithub.com/hashicorp/terraform/issues/29972)) - `terraform show -json`: JSON plan output now correctly maps aliased providers to their configurations, and includes the full provider source address alongside the short provider name. ([#30138](https://togithub.com/hashicorp/terraform/issues/30138)) - The local token configuration in the `cloud` and `remote` backend now has higher priority than a token specified in a `credentials` block in the CLI configuration. ([#30664](https://togithub.com/hashicorp/terraform/issues/30664)) - The `cloud` integration now gracefully exits when `-input=false` and an operation requires some user input. - Terraform will now reliably detect an inteerruptiong (e.g. Ctrl+C) during planning for `terraform apply -auto-approve`. Previously there was a window of time where interruption would cancel the plan step but not prevent Terraform from proceeding to the apply step. ([#30979](https://togithub.com/hashicorp/terraform/issues/30979)) - Terraform will no longer crash if a provider fails to return a schema. ([#30987](https://togithub.com/hashicorp/terraform/issues/30987)) ### [`v1.1.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.8...v1.1.9) ##### 1.1.9 (April 20, 2022) BUG FIXES: - cli: Fix crash when using sensitive values in sets. ([#30825](https://togithub.com/hashicorp/terraform/issues/30825)) - cli: Fix double-quoted map keys when rendering a diff. ([#30855](https://togithub.com/hashicorp/terraform/issues/30855)) - core: Prevent errors when handling a data source with incompatible schema changes ([#30830](https://togithub.com/hashicorp/terraform/issues/30830)) ENHANCEMENTS: - cli: Terraform now supports [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks), a Terraform Cloud integration for executing remote operations, for the post plan stage of a run. ### [`v1.1.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.7...v1.1.8) ##### 1.1.8 (April 07, 2022) BUG FIXES: - cli: Fix missing identifying attributes (e.g. "id", "name") when displaying plan diffs with nested objects. ([#30685](https://togithub.com/hashicorp/terraform/issues/30685)) - functions: Fix error when `sum()` function is called with a collection of string-encoded numbers, such as `sum(["1", "2", "3"])`. ([#30684](https://togithub.com/hashicorp/terraform/issues/30684)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will no longer crash in the `terraform apply` phase if an error occurs during backend configuration. ([#30780](https://togithub.com/hashicorp/terraform/pull/30780)) ### [`v1.1.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.6...v1.1.7) #### 1.1.7 (March 02, 2022) BUG FIXES: - `terraform show -json`: Improve performance for deeply-nested object values. The previous implementation was accidentally quadratic, which could result in very long execution time for generating JSON plans, and timeouts on Terraform Cloud and Terraform Enterprise. ([#30561](https://togithub.com/hashicorp/terraform/issues/30561)) - cloud: Update go-slug for terraform.tfstate exclusion to prevent a user from getting an error after migrating state to TFC. ### [`v1.1.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.5...v1.1.6) ##### 1.1.6 (February 16, 2022) BUG FIXES: - cli: Prevent complex uses of the console-only `type` function. This function may only be used at the top level of console expressions, to display the type of a given value. Attempting to use this function in complex expressions will now display a diagnostic error instead of crashing. ([#30476](https://togithub.com/hashicorp/terraform/issues/30476)) - `terraform state mv`: Will now correctly exit with error code `1` when the specified resources cannot be found in state. Previously Terraform would display appropriate diagnostic errors, but exit successfully. ([#29365](https://togithub.com/hashicorp/terraform/issues/29365)) ### [`v1.1.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.4...v1.1.5) #### 1.1.5 (February 02, 2022) ENHANCEMENTS: - backend/s3: Update AWS SDK to allow the use of the ap-southeast-3 region ([#30363](https://togithub.com/hashicorp/terraform/issues/30363)) BUG FIXES: - cli: Fix crash when using autocomplete with long commands, such as `terraform workspace select` ([#30193](https://togithub.com/hashicorp/terraform/issues/30193)) ### [`v1.1.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.3...v1.1.4) ##### 1.1.4 (January 19, 2022) BUG FIXES: - config: Non-nullable variables with null inputs were not given default values when checking validation statements ([#30330](https://togithub.com/hashicorp/terraform/issues/30330)) - config: Terraform will no longer incorrectly report "Cross-package move statement" when an external package has changed a resource from no `count` to using `count`, or vice-versa. ([#30333](https://togithub.com/hashicorp/terraform/issues/30333)) ### [`v1.1.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.2...v1.1.3) ##### 1.1.3 (January 06, 2022) BUG FIXES: - `terraform init`: Will now remove from [the dependency lock file](https://www.terraform.io/language/files/dependency-lock) entries for providers not used in the current configuration. Previously it would leave formerly-used providers behind in the lock file, leading to "missing or corrupted provider plugins" errors when other commands verified the consistency of the installed plugins against the locked plugins. ([#30192](https://togithub.com/hashicorp/terraform/issues/30192)) - config: Fix panic when encountering an invalid provider block within a module ([#30095](https://togithub.com/hashicorp/terraform/issues/30095)) - config: Fix cycle error when the index of a module containing move statements is changed ([#30232](https://togithub.com/hashicorp/terraform/issues/30232)) - config: Fix inconsistent ordering with nested move operations ([#30253](https://togithub.com/hashicorp/terraform/issues/30253)) - config: Fix `moved` block refactoring to include nested modules ([#30233](https://togithub.com/hashicorp/terraform/issues/30233)) - functions: Redact sensitive values from function call error messages ([#30067](https://togithub.com/hashicorp/terraform/issues/30067)) - `terraform show`: Disable plan state lineage checks, ensuring that we can show plan files which were generated against non-default state files ([#30205](https://togithub.com/hashicorp/terraform/issues/30205)) ### [`v1.1.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.1...v1.1.2) ##### 1.1.2 (December 17, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to this new version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. BUG FIXES: - config: Fix panic when using `-target` in combination with `moved` blocks within modules ([#30189](https://togithub.com/hashicorp/terraform/issues/30189)) - core: Fix condition which could lead to an empty state being written when there is a failure building the apply graph ([#30199](https://togithub.com/hashicorp/terraform/issues/30199)) ### [`v1.1.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.0...v1.1.1) ##### 1.1.1 (December 15, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** BUG FIXES: - core: Fix crash with orphaned module instance due to changed `count` or `for_each` value ([#30151](https://togithub.com/hashicorp/terraform/issues/30151)) - core: Fix regression where some expressions failed during validation when referencing resources expanded with `count` or `for_each` ([#30171](https://togithub.com/hashicorp/terraform/issues/30171)) ### [`v1.1.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.11...v1.1.0) ##### 1.1.0 (December 08, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** Terraform v1.1.0 is a new minor release, containing some new features and some bug fixes whose scope was too large for inclusion in a patch release. NEW FEATURES: - `moved` blocks for refactoring within modules: Module authors can now record in module source code whenever they've changed the address of a resource or resource instance, and then during planning Terraform will automatically migrate existing objects in the state to new addresses. This therefore avoids the need for users of a shared module to manually run `terraform state mv` after upgrading to a version of the module, as long as the change is expressible as static configuration. However, `terraform state mv` will remain available for use in more complex migration situations that are not well-suited to declarative configuration. - A new `cloud` block in the `terraform` settings block introduces a native Terraform Cloud integration for the [CLI-driven run workflow](https://www.terraform.io/docs/cloud/run/cli.html). The Cloud integration includes several enhancements, including per-run variable support using the `-var` flag, the ability to map Terraform Cloud workspaces to the current configuration via [Workspace Tags](https://www.terraform.io/docs/cloud/api/workspaces.html#get-tags), and an improved user experience for Terraform Cloud and Enterprise users with actionable error messages and prompts. - `terraform plan` and `terraform apply` both now include additional annotations for resource instances planned for deletion to explain why Terraform has proposed that action. For example, if you change the `count` argument for a resource to a lower number then Terraform will now mention that as part of proposing to destroy any existing objects that exceed the new count. UPGRADE NOTES: This release is covered by the [Terraform v1.0 Compatibility Promises](https://www.terraform.io/docs/language/v1-compatibility-promises.html), but does include some changes permitted within those promises as described below. - Terraform on macOS now requires macOS 10.13 High Sierra or later; Older macOS versions are no longer supported. - The `terraform graph` command no longer supports `-type=validate` and `-type=eval` options. The validate graph is always the same as the plan graph anyway, and the "eval" graph was just an implementation detail of the `terraform console` command. The default behavior of creating a plan graph should be a reasonable replacement for both of the removed graph modes. (Please note that `terraform graph` is not covered by the Terraform v1.0 compatibility promises, because its behavior inherently exposes Terraform Core implementation details, so we recommend it only for interactive debugging tasks and not for use in automation.) - `terraform apply` with a previously-saved plan file will now verify that the provider plugin packages used to create the plan fully match the ones used during apply, using the same checksum scheme that Terraform normally uses for the dependency lock file. Previously Terraform was checking consistency of plugins from a plan file using a legacy mechanism which covered only the main plugin executable, not any other files that might be distributed alongside in the plugin package. This additional check should not affect typical plugins that conform to the expectation that a plugin package's contents are immutable once released, but may affect a hypothetical in-house plugin that intentionally modifies extra files in its package directory somehow between plan and apply. If you have such a plugin, you'll need to change its approach to store those files in some other location separate from the package directory. This is a minor compatibility break motivated by increasing the assurance that plugins have not been inadvertently or maliciously modified between plan and apply. - `terraform state mv` will now error when legacy `-backup` or `-backup-out` options are used without the `-state` option on non-local backends. These options operate on a local state file only. Previously, these options were accepted but ignored silently when used with non-local backends. - In the AzureRM backend, the new opt-in option `use_microsoft_graph` switches to using MSAL authentication tokens and Microsoft Graph rather than using ADAL tokens and Azure Active Directory Graph, which is now [deprecated by Microsoft](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq). The new mode will become the default in Terraform v1.2, so please plan to migrate to using this setting and test with your own Azure AD tenant prior to the Terraform v1.2 release. ENHANCEMENTS: - config: Terraform now checks the syntax of and normalizes module source addresses (the `source` argument in `module` blocks) during configuration decoding rather than only at module installation time. This is largely just an internal refactoring, but a visible benefit of this change is that the `terraform init` messages about module downloading will now show the canonical module package address Terraform is downloading from, after interpreting the special shorthands for common cases like GitHub URLs. ([#28854](https://togithub.com/hashicorp/terraform/issues/28854)) - config: Variables can now be declared as "nullable", which defines whether a variable can be null within a module. Setting `nullable = false` ensures that a variable value will never be `null`, and may instead take on the variable's default value if the caller sets it explicitly to `null`. ([#29832](https://togithub.com/hashicorp/terraform/issues/29832)) - `terraform plan` and `terraform apply`: When Terraform plans to destroy a resource instance due to it no longer being declared in the configuration, the proposed plan output will now include a note hinting at what situation prompted that proposal, so you can more easily see what configuration change might avoid the object being destroyed. ([#29637](https://togithub.com/hashicorp/terraform/pull/29637)) - `terraform plan` and `terraform apply`: Terraform will now report explicitly in the UI if it automatically moves a resource instance to a new address as a result of adding or removing the `count` argument from an existing resource. For example, if you previously had `resource "aws_subnet" "example"` *without* `count`, you might have `aws_subnet.example` already bound to a remote object in your state. If you add `count = 1` to that resource then Terraform would previously silently rebind the object to `aws_subnet.example[0]` as part of planning, whereas now Terraform will mention that it did so explicitly in the plan description. ([#29605](https://togithub.com/hashicorp/terraform/issues/29605)) - `terraform workspace delete`: will now allow deleting a workspace whose state contains only data resource instances and output values, without running `terraform destroy` first. Previously the presence of data resources would require using `-force` to override the safety check guarding against accidentally forgetting about remote objects, but a data resource is not responsible for the management of its associated remote object(s) and so there's no reason to require explicit deletion. ([#29754](https://togithub.com/hashicorp/terraform/issues/29754)) - `terraform validate`: Terraform now uses precise type information for resources during config validation, allowing more problems to be caught that that step rather than only during the planning step. ([#29862](https://togithub.com/hashicorp/terraform/issues/29862)) - provisioner/remote-exec and provisioner/file: When using SSH agent authentication mode on Windows, Terraform can now detect and use [the Windows 10 built-in OpenSSH Client](https://devblogs.microsoft.com/powershell/using-the-openssh-beta-in-windows-10-fall-creators-update-and-windows-server-1709/)'s SSH Agent, when available, in addition to the existing support for the third-party solution [Pageant](https://documentation.help/PuTTY/pageant.html) that was already supported. ([#29747](https://togithub.com/hashicorp/terraform/issues/29747)) - cli: `terraform state mv` will now return an error for `-backup` or `-backup-out` options used without the `-state` option, unless the working directory is initialized to use the local backend. Previously Terraform would silently ignore those options, since they are applicable only to the local backend. ([#27908](https://togithub.com/hashicorp/terraform/issues/27908)) - `terraform console`: now has a new `type()` function, available only in the interactive console, for inspecting the exact type of a particular value as an aid to debugging. ([#28501](https://togithub.com/hashicorp/terraform/issues/28501)) BUG FIXES: - config: `ignore_changes = all` now works in override files. ([#29849](https://togithub.com/hashicorp/terraform/issues/29849)) - config: Upgrading an unknown single value to a list using a splat expression now correctly returns an unknown value and type. Previously it would sometimes "overpromise" a particular return type, leading to an inconsistency error during the apply step. ([#30062](https://togithub.com/hashicorp/terraform/issues/30062)) - config: Terraform is now more precise in its detection of data resources that must be deferred to the apply step due to their `depends_on` arguments referring to not-yet-converged managed resources. ([#29682](https://togithub.com/hashicorp/terraform/issues/29682)) - config: `ignore_changes` can no longer cause a null map to be converted to an empty map, which would otherwise potentially cause surprising side-effects in provider logic. ([#29928](https://togithub.com/hashicorp/terraform/issues/29928)) - core: Provider configuration obtained from interactive prompts will now be merged properly with settings given in the configuration. Previously this merging was incorrect in some cases. ([#29000](https://togithub.com/hashicorp/terraform/issues/29000)) - `terraform plan`: Improved rendering of changes inside attributes that accept lists, sets, or maps of nested object types. ([#29827](https://togithub.com/hashicorp/terraform/issues/29827), [#29983](https://togithub.com/hashicorp/terraform/issues/29983), [#29986](https://togithub.com/terraform/issues/29986)) - `terraform apply`: Will no longer try to apply a stale plan that was generated against an originally-empty state. Previously this was an unintended exception to the rule that a plan can only be applied to the state snapshot it was generated against. ([#29755](https://togithub.com/hashicorp/terraform/issues/29755)) - `terraform show -json`: Attributes that are declared as using the legacy [Attributes as Blocks](https://www.terraform.io/docs/language/attr-as-blocks.html) behavior are now represented more faithfully in the JSON plan output. ([#29522](https://togithub.com/hashicorp/terraform/issues/29522)) - `terraform init`: Will now update the backend configuration hash value at a more approprimate time, to ensure properly restarting a backend migration process that failed on the first attempt. ([#29860](https://togithub.com/hashicorp/terraform/issues/29860)) - backend/oss: Flatten `assume_role` block arguments, so that they are more compatible with the `terraform_remote_state` data source. ([#29307](https://togithub.com/hashicorp/terraform/issues/29307)) ### [`v1.0.11`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.11) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.10...v1.0.11) ##### 1.0.11 (November 10, 2021) ENHANCEMENTS: - backend/oss: Added support for `sts_endpoint` ([#29841](https://togithub.com/hashicorp/terraform/issues/29841)) BUG FIXES: - config: Fixed a bug in which `ignore_changes = all` would not work in override files ([#29849](https://togithub.com/hashicorp/terraform/issues/29849)) - config: Numbers are now compared for equality based on their protocol representation, eliminating unexpected changes due to small precision errors ([#29864](https://togithub.com/hashicorp/terraform/issues/29864)) ### [`v1.0.10`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.10) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.9...v1.0.10) ##### 1.0.10 (October 28, 2021) BUG FIXES: - backend/oss: Fix panic w </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/nairb774/terraform-provider-flipflop).

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [hashicorp/terraform](https://togithub.com/hashicorp/terraform) | docker | minor | `1.0.8` -> `1.3.6` | --- ### Release Notes <details> <summary>hashicorp/terraform</summary> ### [`v1.3.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.5...v1.3.6) #### 1.3.6 (November 30, 2022) BUG FIXES: - Terraform could crash if an orphaned resource instance was deleted externally and had condition checks in the configuration ([#32246](https://togithub.com/hashicorp/terraform/issues/32246)) - Module output changes were being removed and re-added to the stored plan, impacting performance with large numbers of outputs ([#32307](https://togithub.com/hashicorp/terraform/issues/32307)) ### [`v1.3.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.4...v1.3.5) ##### 1.3.5 (November 17, 2022) BUG FIXES: - Prevent crash while serializing the plan for an empty destroy operation ([#32207](https://togithub.com/hashicorp/terraform/issues/32207)) - Allow a destroy plan to refresh instances while taking into account that some may no longer exist ([#32208](https://togithub.com/hashicorp/terraform/issues/32208)) - Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix inconsistent behaviour in empty vs null collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Prevent file uploads from creating unneeded temporary files when the payload size is known ([#32206](https://togithub.com/hashicorp/terraform/issues/32206)) - Nested attributes marked sensitive by schema no longer reveal sub-attributes in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Nested attributes now more consistently display when they become unknown or null values in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Sensitive values are now always displayed as `(sensitive value)` instead of sometimes as `(sensitive)` \[GH32004] ### [`v1.3.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.3...v1.3.4) #### 1.3.4 (November 02, 2022) BUG FIXES: - Fix invalid refresh-only plan caused by data sources being deferred to apply ([#32111](https://togithub.com/hashicorp/terraform/issues/32111)) - Optimize the handling of condition checks during apply to prevent performance regressions with large numbers of instances ([#32123](https://togithub.com/hashicorp/terraform/issues/32123)) - Output preconditions should not be evaluated during destroy ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Fix crash from `console` when outputs contain preconditions ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Destroy with no state would still attempt to evaluate some values ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Prevent unnecessary evaluation and planning of resources during the pre-destroy refresh ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - AzureRM Backend: support for generic OIDC authentication via the `oidc_token` and `oidc_token_file_path` properties ([#31966](https://togithub.com/hashicorp/terraform/issues/31966)) - Input and Module Variables: Convert variable types before attempting to apply default values. ([#32027](https://togithub.com/hashicorp/terraform/issues/32027)) - When installing remote module packages delivered in tar format, Terraform now limits the tar header block size to 1MiB to avoid unbounded memory usage for maliciously-crafted module packages. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform will now reject excessively-complex regular expression patterns passed to the `regex`, `regexall`, and `replace` functions, to avoid unbounded memory usage for maliciously-crafted patterns. This change should not affect any reasonable patterns intended for practical use. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform on Windows now rejects invalid environment variables whose values contain the NUL character when propagating environment variables to a child process such as a provider plugin. Previously Terraform would incorrectly treat that character as a separator between two separate environment variables. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) ### [`v1.3.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.2...v1.3.3) #### 1.3.3 (October 19, 2022) BUG FIXES: - Fix error when removing a resource from configuration which has according to the provider has already been deleted. ([#31850](https://togithub.com/hashicorp/terraform/issues/31850)) - Fix error when setting empty collections into variables with collections of nested objects with default values. ([#32033](https://togithub.com/hashicorp/terraform/issues/32033)) ### [`v1.3.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.1...v1.3.2) #### 1.3.2 (October 06, 2022) BUG FIXES: - Fixed a crash caused by Terraform incorrectly re-registering output value preconditions during the apply phase (rather than just reusing the already-planned checks from the plan phase). ([#31890](https://togithub.com/hashicorp/terraform/issues/31890)) - Prevent errors when the provider reports that a deposed instance no longer exists ([#31902](https://togithub.com/hashicorp/terraform/issues/31902)) - Using `ignore_changes = all` could cause persistent diffs with legacy providers ([#31914](https://togithub.com/hashicorp/terraform/issues/31914)) - Fix cycles when resource dependencies cross over between independent provider configurations ([#31917](https://togithub.com/hashicorp/terraform/issues/31917)) - Improve handling of missing resource instances during `import` ([#31878](https://togithub.com/hashicorp/terraform/issues/31878)) ### [`v1.3.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.0...v1.3.1) #### 1.3.1 (September 28, 2022) NOTE: - On `darwin/amd64` and `darwin/arm64` architectures, `terraform` binaries are now built with CGO enabled. This should not have any user-facing impact, except in cases where the pure Go DNS resolver causes problems on recent versions of macOS: using CGO may mitigate these issues. Please see the upstream bug [https://github.com/golang/go/issues/52839](https://togithub.com/golang/go/issues/52839) for more details. BUG FIXES: - Fixed a crash when using objects with optional attributes and default values in collections, most visible with nested modules. ([#31847](https://togithub.com/hashicorp/terraform/issues/31847)) - Prevent cycles in some situations where a provider depends on resources in the configuration which are participating in planned changes. ([#31857](https://togithub.com/hashicorp/terraform/issues/31857)) - Fixed an error when attempting to destroy a configuration where resources do not exist in the state. ([#31858](https://togithub.com/hashicorp/terraform/issues/31858)) - Data sources which cannot be read during will no longer prevent the state from being serialized. ([#31871](https://togithub.com/hashicorp/terraform/issues/31871)) - Fixed a crash which occured when a resource with a precondition and/or a postcondition appeared inside a module with two or more instances. ([#31860](https://togithub.com/hashicorp/terraform/issues/31860)) ### [`v1.3.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.9...v1.3.0) #### 1.3.0 (September 21, 2022) NEW FEATURES: - **Optional attributes for object type constraints:** When declaring an input variable whose type constraint includes an object type, you can now declare individual attributes as optional, and specify a default value to use if the caller doesn't set it. For example: ```terraform variable "with_optional_attribute" { type = object({ a = string # a required attribute b = optional(string) # an optional attribute c = optional(number, 127) # an optional attribute with a default value }) } ``` Assigning `{ a = "foo" }` to this variable will result in the value `{ a = "foo", b = null, c = 127 }`. - Added functions: `startswith` and `endswith` allow you to check whether a given string has a specified prefix or suffix. ([#31220](https://togithub.com/hashicorp/terraform/issues/31220)) UPGRADE NOTES: - `terraform show -json`: Output changes now include more detail about the unknown-ness of the planned value. Previously, a planned output would be marked as either fully known or partially unknown, with the `after_unknown` field having value `false` or `true` respectively. Now outputs correctly expose the full structure of unknownness for complex values, allowing consumers of the JSON output format to determine which values in a collection are known only after apply. - `terraform import`: The `-allow-missing-config` has been removed, and at least an empty configuration block must exist to import a resource. - Consumers of the JSON output format expecting on the `after_unknown` field to be only `false` or `true` should be updated to support [the change representation](https://www.terraform.io/internals/json-format#change-representation) described in the documentation, and as was already used for resource changes. ([#31235](https://togithub.com/hashicorp/terraform/issues/31235)) - AzureRM Backend: This release concludes [the deprecation cycle started in Terraform v1.1](https://www.terraform.io/language/upgrade-guides/1-1#preparation-for-removing-azure-ad-graph-support-in-the-azurerm-backend) for the `azurerm` backend's support of "ADAL" authentication. This backend now supports only "MSAL" (Microsoft Graph) authentication. This follows from [Microsoft's own deprecation of Azure AD Graph](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq), and so you must follow the migration instructions presented in that Azure documentation to adopt Microsoft Graph and then change your backend configuration to use MSAL authentication before upgrading to Terraform v1.3. - When making requests to HTTPS servers, Terraform will now reject invalid handshakes that have duplicate extensions, as required by RFC 5246 section 7.4.1.4 and RFC 8446 section 4.2. This may cause new errors when interacting with existing buggy or misconfigured TLS servers, but should not affect correct servers. This only applies to requests made directly by Terraform CLI, such as provider installation and remote state storage. Terraform providers are separate programs which decide their own policy for handling of TLS handshakes. - The following backends, which were deprecated in v1.2.3, have now been removed: `artifactory`, `etcd`, `etcdv3`, `manta`, `swift`. The legacy backend name `azure` has also been removed, because the current Azure backend is named `azurerm`. ([#31711](https://togithub.com/hashicorp/terraform/issues/31711)) ENHANCEMENTS: - config: Optional attributes for object type constraints, as described under new features above. ([#31154](https://togithub.com/hashicorp/terraform/issues/31154)) - config: New built-in function `timecmp` allows determining the ordering relationship between two timestamps while taking potentially-different UTC offsets into account. ([#31687](https://togithub.com/hashicorp/terraform/pull/31687)) - config: When reporting an error message related to a function call, Terraform will now include contextual information about the signature of the function that was being called, as an aid to understanding why the call might have failed. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: When reporting an error or warning message that isn't caused by values being unknown or marked as sensitive, Terraform will no longer mention any values having those characteristics in the contextual information presented alongside the error. Terraform will still return this information for the small subset of error messages that are specifically about unknown values or sensitive values being invalid in certain contexts. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: `moved` blocks can now describe resources moving to and from modules in separate module packages. ([#31556](https://togithub.com/hashicorp/terraform/issues/31556)) - `terraform fmt` now accepts multiple target paths, allowing formatting of several individual files at once. ([#31687](https://togithub.com/hashicorp/terraform/issues/31687)) - `terraform init`: provider installation errors now mention which host Terraform was downloading from ([#31524](https://togithub.com/hashicorp/terraform/issues/31524)) - CLI: Terraform will report more explicitly when it is proposing to delete an object due to it having moved to a resource instance that is not currently declared in the configuration. ([#31695](https://togithub.com/hashicorp/terraform/issues/31695)) - CLI: When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about pre-plan run tasks ([#31617](https://togithub.com/hashicorp/terraform/issues/31617)) - The AzureRM Backend now only supports MSAL (and Microsoft Graph) and no longer makes use of ADAL (and Azure Active Directory Graph) for authentication ([#31070](https://togithub.com/hashicorp/terraform/issues/31070)) - The COS backend now supports global acceleration. ([#31425](https://togithub.com/hashicorp/terraform/issues/31425)) - provider plugin protocol: The Terraform CLI now calls `PlanResourceChange` for compatible providers when destroying resource instances. ([#31179](https://togithub.com/hashicorp/terraform/issues/31179)) - As an implementation detail of the Terraform Cloud integration, Terraform CLI will now capture and upload [the JSON integration format for state](https://www.terraform.io/internals/json-format#state-representation) along with any newly-recorded state snapshots, which then in turn allows Terraform Cloud to provide that information to API-based external integrations. ([#31698](https://togithub.com/hashicorp/terraform/issues/31698)) BUG FIXES: - config: Terraform was not previously evaluating preconditions and postconditions during the apply phase for resource instances that didn't have any changes pending, which was incorrect because the outcome of a condition can potentially be affected by changes to *other* objects in the configuration. Terraform will now always check the conditions for every resource instance included in a plan during the apply phase, even for resource instances that have "no-op" changes. This means that some failures that would previously have been detected only by a subsequent run will now be detected during the same run that caused them, thereby giving the feedback at the appropriate time. ([#31491](https://togithub.com/hashicorp/terraform/issues/31491)) - `terraform show -json`: Fixed missing markers for unknown values in the encoding of partially unknown tuples and sets. ([#31236](https://togithub.com/hashicorp/terraform/issues/31236)) - `terraform output` CLI help documentation is now more consistent with web-based documentation. ([#29354](https://togithub.com/hashicorp/terraform/issues/29354)) - `terraform init`: Error messages now handle the situation where the underlying HTTP client library does not indicate a hostname for a failed request. ([#31542](https://togithub.com/hashicorp/terraform/issues/31542)) - `terraform init`: Don't panic if a child module contains a resource with a syntactically-invalid resource type name. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - CLI: The representation of destroying already-`null` output values in a destroy plan will no longer report them as being deleted, which avoids reporting the deletion of an output value that was already absent. ([#31471](https://togithub.com/hashicorp/terraform/issues/31471)) - `terraform import`: Better handling of resources or modules that use `for_each`, and situations where data resources are needed to complete the operation. ([#31283](https://togithub.com/hashicorp/terraform/issues/31283)) EXPERIMENTS: - This release concludes the `module_variable_optional_attrs` experiment, which started in Terraform v0.14.0. The final design of the optional attributes feature is similar to the experimental form in the previous releases, but with two major differences: - The `optional` function-like modifier for declaring an optional attribute now accepts an optional second argument for specifying a default value to use when the attribute isn't set by the caller. If not specified, the default value is a null value of the appropriate type as before. - The built-in `defaults` function, previously used to meet the use-case of replacing null values with default values, will not graduate to stable and has been removed. Use the second argument of `optional` inline in your type constraint to declare default values instead. If you have any experimental modules that were participating in this experiment, you will need to remove the experiment opt-in and adopt the new syntax for declaring default values in order to migrate your existing module to the stablized version of this feature. If you are writing a shared module for others to use, we recommend declaring that your module requires Terraform v1.3.0 or later to give specific feedback when using the new feature on older Terraform versions, in place of the previous declaration to use the experimental form of this feature: ```hcl terraform { required_version = ">= 1.3.0" } ``` ### [`v1.2.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.8...v1.2.9) #### 1.2.9 (September 07, 2022) ENHANCEMENTS: - terraform init: add link to documentation when a checksum is missing from the lock file. ([#31726](https://togithub.com/hashicorp/terraform/issues/31726)) ### [`v1.2.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.7...v1.2.8) #### 1.2.8 (August 24, 2022) BUG FIXES: - config: The `flatten` function will no longer panic if given a null value that has been explicitly converted to or implicitly inferred as having a list, set, or tuple type. Previously Terraform would panic in such a situation because it tried to "flatten" the contents of the null value into the result, which is impossible. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) - config: The `tolist`, `toset`, and `tomap` functions, and various automatic conversions that include similar logic, will no longer panic when asked to infer an element type that is convertable from both a tuple type and a list type whose element type is not yet known. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) ### [`v1.2.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.6...v1.2.7) ##### 1.2.7 (August 10, 2022) ENHANCEMENTS: - config: Check for direct references to deprecated computed attributes. ([#31576](https://togithub.com/hashicorp/terraform/issues/31576)) BUG FIXES: - config: Fix an crash if a submodule contains a resource whose implied provider local name contains invalid characters, by adding additional validation rules to turn it into a real error. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - core: Fix some handling of provider schema attributes which use the newer "structural typing" mechanism introduced with protocol version 6, and therefore with the new Terraform Plugin Framework ([#31532](https://togithub.com/hashicorp/terraform/issues/31532)) - command: Add missing output text for applyable refresh plans. ([#31469](https://togithub.com/hashicorp/terraform/issues/31469)) ### [`v1.2.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.5...v1.2.6) #### 1.2.6 (July 27, 2022) ENHANCEMENTS: - Add a warning and guidance when `terraform init` fails to fully populate the `.terraform.lock.hcl` file. ([#31399](https://togithub.com/hashicorp/terraform/issues/31399)) - Add a direct link to the relevant documentation when `terraform init` fails on missing checksums. ([#31408](https://togithub.com/hashicorp/terraform/issues/31408)) BUG FIXES: - Fix panic on `terraform show` when state file is invalid or unavailable. ([#31444](https://togithub.com/hashicorp/terraform/issues/31444)) - Fix `terraform providers lock` command failing on missing checksums. ([#31389](https://togithub.com/hashicorp/terraform/issues/31389)) - Some combinations of move block operations would be executed in the wrong order ([#31499](https://togithub.com/hashicorp/terraform/issues/31499)) - Don't attribute an error to the provider when a computed attribute is listed in `ignore_changes` ([#31509](https://togithub.com/hashicorp/terraform/issues/31509)) ### [`v1.2.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.4...v1.2.5) #### 1.2.5 (July 13, 2022) BUG FIXES: - Report correct error message when a prerelease field is included in the `required_version` global constraint. ([#31331](https://togithub.com/hashicorp/terraform/issues/31331)) - Fix case when extra blank lines were inserted into the plan for unchanged blocks. ([#31330](https://togithub.com/hashicorp/terraform/issues/31330)) ### [`v1.2.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.3...v1.2.4) #### 1.2.4 (June 29, 2022) ENHANCEMENTS: - Improved validation of `required_providers` to prevent single providers from being required with multiple names. ([#31218](https://togithub.com/hashicorp/terraform/issues/31218)) - Improved plan performance by optimizing `addrs.Module.String` for allocations. ([#31293](https://togithub.com/hashicorp/terraform/issues/31293)) BUG FIXES: - backend/http: Fixed bug where the HTTP backend would fail to retry acquiring the state lock and ignored the `-lock-timeout` flag. ([#31256](https://togithub.com/hashicorp/terraform/issues/31256)) - Fix crash if a `precondition` or `postcondition` block omitted the required `condition` argument. ([#31290](https://togithub.com/hashicorp/terraform/issues/31290)) ### [`v1.2.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.2...v1.2.3) ##### 1.2.3 (June 15, 2022) UPGRADE NOTES: - The following remote state backends are now marked as deprecated, and are planned to be removed in a future Terraform release. These backends have been unmaintained since before Terraform v1.0, and may contain known bugs, outdated packages, or security vulnerabilities. - artifactory - etcd - etcdv3 - manta - swift BUG FIXES: - Missing check for error diagnostics in GetProviderSchema could result in panic ([#31184](https://togithub.com/hashicorp/terraform/issues/31184)) - Module registries returning X-Terraform-Get locations with no URL would error with "no getter available for X-Terraform-Get source protocol" ([#31237](https://togithub.com/hashicorp/terraform/issues/31237)) - Fix crash from concurrent operation on shared set of resource instance dependencies ([#31246](https://togithub.com/hashicorp/terraform/issues/31246)) - backend/cos: `tencentcloud-terraform-lock` tag was not removed in all cases ([#31223](https://togithub.com/hashicorp/terraform/issues/31223)) ### [`v1.2.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.1...v1.2.2) ##### 1.2.2 (June 01, 2022) ENHANCEMENTS: - Invalid `-var` arguments with spaces between the name and value now have an improved error message ([#30985](https://togithub.com/hashicorp/terraform/issues/30985)) BUG FIXES: - Terraform now hides invalid input values for sensitive root module variables when generating error diagnostics ([#30552](https://togithub.com/hashicorp/terraform/issues/30552)) - Fixed crash on CLI autocomplete ([#31160](https://togithub.com/hashicorp/terraform/issues/31160)) - The "Configuration contains unknown values" error message now includes attribute paths ([#31111](https://togithub.com/hashicorp/terraform/issues/31111)) ### [`v1.2.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.0...v1.2.1) ##### 1.2.1 (May 23, 2022) BUG FIXES: - SSH provisioner connections fail when using signed `ed25519` keys ([#31092](https://togithub.com/hashicorp/terraform/issues/31092)) - Crash with invalid module source ([#31060](https://togithub.com/hashicorp/terraform/issues/31060)) - Incorrect "Module is incompatible with count, for_each, and depends_on" error when a provider is nested within a module along with a sub-module using `count` or `for_each` ([#31091](https://togithub.com/hashicorp/terraform/issues/31091)) ### [`v1.2.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.9...v1.2.0) ##### 1.2.0 (May 18, 2022) UPGRADE NOTES: - If you use the [third-party credentials helper plugin terraform-credentials-env](https://togithub.com/apparentlymart/terraform-credentials-env), you should disable it as part of upgrading to Terraform v1.2 because similar functionality is now built in to Terraform itself. The new behavior supports the same environment variable naming scheme but has a difference in priority order from the credentials helper: `TF_TOKEN_...` environment variables will now take priority over credentials blocks in CLI configuration and credentials stored automatically by terraform login, which is not true for credentials provided by any credentials helper plugin. If you see Terraform using different credentials after upgrading, check to make sure you do not specify credentials for the same host in multiple locations. If you use the credentials helper in conjunction with the [hashicorp/tfe](https://registry.terraform.io/providers/hashicorp/tfe) Terraform provider to manage Terraform Cloud or Terraform Enterprise objects with Terraform, you should also upgrade to version 0.31 of that provider, which added the corresponding built-in support for these environment variables. - The official Linux packages for the v1.2 series now require Linux kernel version 2.6.32 or later. - When making outgoing HTTPS or other TLS connections as a client, Terraform now requires the server to support TLS v1.2. TLS v1.0 and v1.1 are no longer supported. Any safely up-to-date server should support TLS 1.2, and mainstream web browsers have required it since 2020. - When making outgoing HTTPS or other TLS connections as a client, Terraform will no longer accept CA certificates signed using the SHA-1 hash function. Publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015. (Note: the changes to Terraform's requirements when interacting with TLS servers apply only to requests made by Terraform CLI itself, such as provider/module installation and state storage requests. Terraform provider plugins include their own TLS clients which may have different requirements, and may add new requirements in their own releases, independently of Terraform CLI changes.) NEW FEATURES: - `precondition` and `postcondition` check blocks for resources, data sources, and module output values: module authors can now document assumptions and assertions about configuration and state values. If these conditions are not met, Terraform will report a custom error message to the user and halt further execution. - `replace_triggered_by` is a new `lifecycle` argument for managed resources which triggers replacement of an object based on changes to an upstream dependency. - You can now specify credentials for [Terraform-native services](https://www.terraform.io/internals/remote-service-discovery) using an environment variable named as `TF_TOKEN_` followed by an encoded version of the hostname. For example, Terraform will use variable `TF_TOKEN_app_terraform_io` as a bearer token for requests to "app.terraform.io", for the Terraform Cloud integration and private registry requests. ENHANCEMENTS: - When showing a plan, Terraform CLI will now only show "Changes outside of Terraform" if they relate to resources and resource attributes that contributed to the changes Terraform is proposing to make. ([#30486](https://togithub.com/hashicorp/terraform/issues/30486)) - Error messages for preconditions, postconditions, and custom variable validations are now evaluated as expressions, allowing interpolation of relevant values into the output. ([#30613](https://togithub.com/hashicorp/terraform/issues/30613)) - When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about post-plan [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks). ([#30141](https://togithub.com/hashicorp/terraform/issues/30141)) - Terraform will now show a slightly different note in the plan output if a data resource read is deferred to the apply step due to it depending on a managed resource that has changes pending. ([#30971](https://togithub.com/hashicorp/terraform/issues/30971)) - The "Invalid for_each argument" error message for unknown maps/sets now includes an additional paragraph to try to help the user notice they can move apply-time values into the map *values* instead of the map *keys*, and thus avoid the problem without resorting to `-target`. ([#30327](https://togithub.com/hashicorp/terraform/issues/30327)) - There are some small improvements to the error and warning messages Terraform will emit in the case of invalid provider configuration passing between modules. There are no changes to which situations will produce errors and warnings, but the messages now include additional information intended to clarify what problem Terraform is describing and how to address it. ([#30639](https://togithub.com/hashicorp/terraform/issues/30639)) - The environment variables `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` now serve as fallbacks for the arguments of the same name inside a `cloud` block configuring integration with Terraform Cloud. - The environment variable `TF_WORKSPACE` will now additionally serve as an implicit configuration of a single selected workspace on Terraform Cloud if (and only if) the `cloud` block does not include an explicit workspaces configuration. - The AzureRM Backend now defaults to using MSAL (and Microsoft Graph) rather than ADAL (and Azure Active Directory Graph) for authentication. ([#30891](https://togithub.com/hashicorp/terraform/issues/30891)) - The AzureRM Backend now supports authenticating as a service principal using OpenID Connect. ([#30936](https://togithub.com/hashicorp/terraform/pull/30936)) - When running on macOS, Terraform will now use platform APIs to validate certificates presented by TLS (HTTPS) servers. This may change exactly which root certificates Terraform will accept as valid. ([#30768](https://togithub.com/hashicorp/terraform/issues/30768)) - Show remote host in error message for clarity when installation of provider fails ([#30810](https://togithub.com/hashicorp/terraform/issues/30810)) - Terraform now prints a warning when adding an attribute to `ignore_changes` that is managed only by the provider. Specifying non-configurable attributes in `ignore_changes` has no effect because `ignore_changes` tells Terraform to ignore future changes made in the configuration. ([#30517](https://togithub.com/hashicorp/terraform/issues/30517)) - `terraform show -json` now includes exact type information for output values. ([#30945](https://togithub.com/hashicorp/terraform/issues/30945)) - The `ssh` provisioner connection now supports SSH over HTTP proxy. ([#30274](https://togithub.com/hashicorp/terraform/pull/30274)) - - The SSH client for provisioners now supports newer key algorithms, allowing it to connect to servers running more recent versions of OpenSSH. ([#30962](https://togithub.com/hashicorp/terraform/issues/30962)) BUG FIXES: - Terraform now handles type constraints, nullability, and custom variable validation properly for root module variables. Previously there was an order of operations problem where the nullability and custom variable validation were checked too early, prior to dealing with the type constraints, and thus that logic could potentially "see" an incorrectly-typed value in spite of the type constraint, leading to incorrect errors. ([#29959](https://togithub.com/hashicorp/terraform/issues/29959)) - When reporting a type mismatch between the true and false results of a conditional expression when both results are of the same structural type kind (object/tuple, or a collection thereof), Terraform will no longer return a confusing message like "the types are object and object, respectively", and will instead attempt to explain how the two structural types differ. ([#30920](https://togithub.com/hashicorp/terraform/issues/30920)) - Applying the various type conversion functions like `tostring`, `tonumber`, etc to `null` will now return a null value of the intended type. For example, `tostring(null)` converts from a null value of an unknown type to a null value of string type. Terraform can often handle such conversions automatically when needed, but explicit annotations like this can help Terraform to understand author intent when inferring type conversions for complex-typed values. ([#30879](https://togithub.com/hashicorp/terraform/issues/30879)) - Terraform now returns an error when `cidrnetmask()` is called with an IPv6 address, as it was previously documented to do. IPv6 standards do not preserve the "netmask" syntax sometimes used for IPv4 network configuration; use CIDR prefix syntax instead. ([#30703](https://togithub.com/hashicorp/terraform/issues/30703)) - When performing advanced state management with the `terraform state` commands, Terraform now checks the `required_version` field in the configuration before proceeding. ([#30511](https://togithub.com/hashicorp/terraform/pull/30511)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will now prioritize local terraform variables over remote terraform variables in operations such as `import`, `plan`, `refresh` and `apply` for workspaces in local execution mode. This behavior applies to both `remote` backend and the `cloud` integration configuration. ([#29972](https://togithub.com/hashicorp/terraform/issues/29972)) - `terraform show -json`: JSON plan output now correctly maps aliased providers to their configurations, and includes the full provider source address alongside the short provider name. ([#30138](https://togithub.com/hashicorp/terraform/issues/30138)) - The local token configuration in the `cloud` and `remote` backend now has higher priority than a token specified in a `credentials` block in the CLI configuration. ([#30664](https://togithub.com/hashicorp/terraform/issues/30664)) - The `cloud` integration now gracefully exits when `-input=false` and an operation requires some user input. - Terraform will now reliably detect an inteerruptiong (e.g. Ctrl+C) during planning for `terraform apply -auto-approve`. Previously there was a window of time where interruption would cancel the plan step but not prevent Terraform from proceeding to the apply step. ([#30979](https://togithub.com/hashicorp/terraform/issues/30979)) - Terraform will no longer crash if a provider fails to return a schema. ([#30987](https://togithub.com/hashicorp/terraform/issues/30987)) ### [`v1.1.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.8...v1.1.9) ##### 1.1.9 (April 20, 2022) BUG FIXES: - cli: Fix crash when using sensitive values in sets. ([#30825](https://togithub.com/hashicorp/terraform/issues/30825)) - cli: Fix double-quoted map keys when rendering a diff. ([#30855](https://togithub.com/hashicorp/terraform/issues/30855)) - core: Prevent errors when handling a data source with incompatible schema changes ([#30830](https://togithub.com/hashicorp/terraform/issues/30830)) ENHANCEMENTS: - cli: Terraform now supports [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks), a Terraform Cloud integration for executing remote operations, for the post plan stage of a run. ### [`v1.1.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.7...v1.1.8) ##### 1.1.8 (April 07, 2022) BUG FIXES: - cli: Fix missing identifying attributes (e.g. "id", "name") when displaying plan diffs with nested objects. ([#30685](https://togithub.com/hashicorp/terraform/issues/30685)) - functions: Fix error when `sum()` function is called with a collection of string-encoded numbers, such as `sum(["1", "2", "3"])`. ([#30684](https://togithub.com/hashicorp/terraform/issues/30684)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will no longer crash in the `terraform apply` phase if an error occurs during backend configuration. ([#30780](https://togithub.com/hashicorp/terraform/pull/30780)) ### [`v1.1.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.6...v1.1.7) ##### 1.1.7 (March 02, 2022) BUG FIXES: - `terraform show -json`: Improve performance for deeply-nested object values. The previous implementation was accidentally quadratic, which could result in very long execution time for generating JSON plans, and timeouts on Terraform Cloud and Terraform Enterprise. ([#30561](https://togithub.com/hashicorp/terraform/issues/30561)) - cloud: Update go-slug for terraform.tfstate exclusion to prevent a user from getting an error after migrating state to TFC. ### [`v1.1.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.5...v1.1.6) ##### 1.1.6 (February 16, 2022) BUG FIXES: - cli: Prevent complex uses of the console-only `type` function. This function may only be used at the top level of console expressions, to display the type of a given value. Attempting to use this function in complex expressions will now display a diagnostic error instead of crashing. ([#30476](https://togithub.com/hashicorp/terraform/issues/30476)) - `terraform state mv`: Will now correctly exit with error code `1` when the specified resources cannot be found in state. Previously Terraform would display appropriate diagnostic errors, but exit successfully. ([#29365](https://togithub.com/hashicorp/terraform/issues/29365)) ### [`v1.1.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.4...v1.1.5) ##### 1.1.5 (February 02, 2022) ENHANCEMENTS: - backend/s3: Update AWS SDK to allow the use of the ap-southeast-3 region ([#30363](https://togithub.com/hashicorp/terraform/issues/30363)) BUG FIXES: - cli: Fix crash when using autocomplete with long commands, such as `terraform workspace select` ([#30193](https://togithub.com/hashicorp/terraform/issues/30193)) ### [`v1.1.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.3...v1.1.4) ##### 1.1.4 (January 19, 2022) BUG FIXES: - config: Non-nullable variables with null inputs were not given default values when checking validation statements ([#30330](https://togithub.com/hashicorp/terraform/issues/30330)) - config: Terraform will no longer incorrectly report "Cross-package move statement" when an external package has changed a resource from no `count` to using `count`, or vice-versa. ([#30333](https://togithub.com/hashicorp/terraform/issues/30333)) ### [`v1.1.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.2...v1.1.3) #### 1.1.3 (January 06, 2022) BUG FIXES: - `terraform init`: Will now remove from [the dependency lock file](https://www.terraform.io/language/files/dependency-lock) entries for providers not used in the current configuration. Previously it would leave formerly-used providers behind in the lock file, leading to "missing or corrupted provider plugins" errors when other commands verified the consistency of the installed plugins against the locked plugins. ([#30192](https://togithub.com/hashicorp/terraform/issues/30192)) - config: Fix panic when encountering an invalid provider block within a module ([#30095](https://togithub.com/hashicorp/terraform/issues/30095)) - config: Fix cycle error when the index of a module containing move statements is changed ([#30232](https://togithub.com/hashicorp/terraform/issues/30232)) - config: Fix inconsistent ordering with nested move operations ([#30253](https://togithub.com/hashicorp/terraform/issues/30253)) - config: Fix `moved` block refactoring to include nested modules ([#30233](https://togithub.com/hashicorp/terraform/issues/30233)) - functions: Redact sensitive values from function call error messages ([#30067](https://togithub.com/hashicorp/terraform/issues/30067)) - `terraform show`: Disable plan state lineage checks, ensuring that we can show plan files which were generated against non-default state files ([#30205](https://togithub.com/hashicorp/terraform/issues/30205)) ### [`v1.1.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.1...v1.1.2) ##### 1.1.2 (December 17, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to this new version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. BUG FIXES: - config: Fix panic when using `-target` in combination with `moved` blocks within modules ([#30189](https://togithub.com/hashicorp/terraform/issues/30189)) - core: Fix condition which could lead to an empty state being written when there is a failure building the apply graph ([#30199](https://togithub.com/hashicorp/terraform/issues/30199)) ### [`v1.1.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.0...v1.1.1) #### 1.1.1 (December 15, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** BUG FIXES: - core: Fix crash with orphaned module instance due to changed `count` or `for_each` value ([#30151](https://togithub.com/hashicorp/terraform/issues/30151)) - core: Fix regression where some expressions failed during validation when referencing resources expanded with `count` or `for_each` ([#30171](https://togithub.com/hashicorp/terraform/issues/30171)) ### [`v1.1.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.11...v1.1.0) #### 1.1.0 (December 08, 2021) **If you are using Terraform CLI v1.1.0 or v1.1.1, please upgrade to the latest version as soon as possible.** Terraform CLI v1.1.0 and v1.1.1 both have a bug where a failure to construct the apply-time graph can cause Terraform to incorrectly report success and save an empty state, effectively "forgetting" all existing infrastructure. Although configurations that already worked on previous releases should not encounter this problem, it's possible that incorrect *future* configuration changes would trigger this behavior during the apply step. *** Terraform v1.1.0 is a new minor release, containing some new features and some bug fixes whose scope was too large for inclusion in a patch release. NEW FEATURES: - `moved` blocks for refactoring within modules: Module authors can now record in module source code whenever they've changed the address of a resource or resource instance, and then during planning Terraform will automatically migrate existing objects in the state to new addresses. This therefore avoids the need for users of a shared module to manually run `terraform state mv` after upgrading to a version of the module, as long as the change is expressible as static configuration. However, `terraform state mv` will remain available for use in more complex migration situations that are not well-suited to declarative configuration. - A new `cloud` block in the `terraform` settings block introduces a native Terraform Cloud integration for the [CLI-driven run workflow](https://www.terraform.io/docs/cloud/run/cli.html). The Cloud integration includes several enhancements, including per-run variable support using the `-var` flag, the ability to map Terraform Cloud workspaces to the current configuration via [Workspace Tags](https://www.terraform.io/docs/cloud/api/workspaces.html#get-tags), and an improved user experience for Terraform Cloud and Enterprise users with actionable error messages and prompts. - `terraform plan` and `terraform apply` both now include additional annotations for resource instances planned for deletion to explain why Terraform has proposed that action. For example, if you change the `count` argument for a resource to a lower number then Terraform will now mention that as part of proposing to destroy any existing objects that exceed the new count. UPGRADE NOTES: This release is covered by the [Terraform v1.0 Compatibility Promises](https://www.terraform.io/docs/language/v1-compatibility-promises.html), but does include some changes permitted within those promises as described below. - Terraform on macOS now requires macOS 10.13 High Sierra or later; Older macOS versions are no longer supported. - The `terraform graph` command no longer supports `-type=validate` and `-type=eval` options. The validate graph is always the same as the plan graph anyway, and the "eval" graph was just an implementation detail of the `terraform console` command. The default behavior of creating a plan graph should be a reasonable replacement for both of the removed graph modes. (Please note that `terraform graph` is not covered by the Terraform v1.0 compatibility promises, because its behavior inherently exposes Terraform Core implementation details, so we recommend it only for interactive debugging tasks and not for use in automation.) - `terraform apply` with a previously-saved plan file will now verify that the provider plugin packages used to create the plan fully match the ones used during apply, using the same checksum scheme that Terraform normally uses for the dependency lock file. Previously Terraform was checking consistency of plugins from a plan file using a legacy mechanism which covered only the main plugin executable, not any other files that might be distributed alongside in the plugin package. This additional check should not affect typical plugins that conform to the expectation that a plugin package's contents are immutable once released, but may affect a hypothetical in-house plugin that intentionally modifies extra files in its package directory somehow between plan and apply. If you have such a plugin, you'll need to change its approach to store those files in some other location separate from the package directory. This is a minor compatibility break motivated by increasing the assurance that plugins have not been inadvertently or maliciously modified between plan and apply. - `terraform state mv` will now error when legacy `-backup` or `-backup-out` options are used without the `-state` option on non-local backends. These options operate on a local state file only. Previously, these options were accepted but ignored silently when used with non-local backends. - In the AzureRM backend, the new opt-in option `use_microsoft_graph` switches to using MSAL authentication tokens and Microsoft Graph rather than using ADAL tokens and Azure Active Directory Graph, which is now [deprecated by Microsoft](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq). The new mode will become the default in Terraform v1.2, so please plan to migrate to using this setting and test with your own Azure AD tenant prior to the Terraform v1.2 release. ENHANCEMENTS: - config: Terraform now checks the syntax of and normalizes module source addresses (the `source` argument in `module` blocks) during configuration decoding rather than only at module installation time. This is largely just an internal refactoring, but a visible benefit of this change is that the `terraform init` messages about module downloading will now show the canonical module package address Terraform is downloading from, after interpreting the special shorthands for common cases like GitHub URLs. ([#28854](https://togithub.com/hashicorp/terraform/issues/28854)) - config: Variables can now be declared as "nullable", which defines whether a variable can be null within a module. Setting `nullable = false` ensures that a variable value will never be `null`, and may instead take on the variable's default value if the caller sets it explicitly to `null`. ([#29832](https://togithub.com/hashicorp/terraform/issues/29832)) - `terraform plan` and `terraform apply`: When Terraform plans to destroy a resource instance due to it no longer being declared in the configuration, the proposed plan output will now include a note hinting at what situation prompted that proposal, so you can more easily see what configuration change might avoid the object being destroyed. ([#29637](https://togithub.com/hashicorp/terraform/pull/29637)) - `terraform plan` and `terraform apply`: Terraform will now report explicitly in the UI if it automatically moves a resource instance to a new address as a result of adding or removing the `count` argument from an existing resource. For example, if you previously had `resource "aws_subnet" "example"` *without* `count`, you might have `aws_subnet.example` already bound to a remote object in your state. If you add `count = 1` to that resource then Terraform would previously silently rebind the object to `aws_subnet.example[0]` as part of planning, whereas now Terraform will mention that it did so explicitly in the plan description. ([#29605](https://togithub.com/hashicorp/terraform/issues/29605)) - `terraform workspace delete`: will now allow deleting a workspace whose state contains only data resource instances and output values, without running `terraform destroy` first. Previously the presence of data resources would require using `-force` to override the safety check guarding against accidentally forgetting about remote objects, but a data resource is not responsible for the management of its associated remote object(s) and so there's no reason to require explicit deletion. ([#29754](https://togithub.com/hashicorp/terraform/issues/29754)) - `terraform validate`: Terraform now uses precise type information for resources during config validation, allowing more problems to be caught that that step rather than only during the planning step. ([#29862](https://togithub.com/hashicorp/terraform/issues/29862)) - provisioner/remote-exec and provisioner/file: When using SSH agent authentication mode on Windows, Terraform can now detect and use [the Windows 10 built-in OpenSSH Client](https://devblogs.microsoft.com/powershell/using-the-openssh-beta-in-windows-10-fall-creators-update-and-windows-server-1709/)'s SSH Agent, when available, in addition to the existing support for the third-party solution [Pageant](https://documentation.help/PuTTY/pageant.html) that was already supported. ([#29747](https://togithub.com/hashicorp/terraform/issues/29747)) - cli: `terraform state mv` will now return an error for `-backup` or `-backup-out` options used without the `-state` option, unless the working directory is initialized to use the local backend. Previously Terraform would silently ignore those options, since they are applicable only to the local backend. ([#27908](https://togithub.com/hashicorp/terraform/issues/27908)) - `terraform console`: now has a new `type()` function, available only in the interactive console, for inspecting the exact type of a particular value as an aid to debugging. ([#28501](https://togithub.com/hashicorp/terraform/issues/28501)) BUG FIXES: - config: `ignore_changes = all` now works in override files. ([#29849](https://togithub.com/hashicorp/terraform/issues/29849)) - config: Upgrading an unknown single value to a list using a splat expression now correctly returns an unknown value and type. Previously it would sometimes "overpromise" a particular return type, leading to an inconsistency error during the apply step. ([#30062](https://togithub.com/hashicorp/terraform/issues/30062)) - config: Terraform is now more precise in its detection of data resources that must be deferred to the apply step due to their `depends_on` arguments referring to not-yet-converged managed resources. ([#29682](https://togithub.com/hashicorp/terraform/issues/29682)) - config: `ignore_changes` can no longer cause a null map to be converted to an empty map, which would otherwise potentially cause surprising side-effects in provider logic. ([#29928](https://togithub.com/hashicorp/terraform/issues/29928)) - core: Provider configuration obtained from interactive prompts will now be merged properly with settings given in the configuration. Previously this merging was incorrect in some cases. ([#29000](https://togithub.com/hashicorp/terraform/issues/29000)) - `terraform plan`: Improved rendering of changes inside attributes that accept lists, sets, or maps of nested object types. ([#29827](https://togithub.com/hashicorp/terraform/issues/29827), [#29983](https://togithub.com/hashicorp/terraform/issues/29983), [#29986](https://togithub.com/terraform/issues/29986)) - `terraform apply`: Will no longer try to apply a stale plan that was generated against an originally-empty state. Previously this was an unintended exception to the rule that a plan can only be applied to the state snapshot it was generated against. ([#29755](https://togithub.com/hashicorp/terraform/issues/29755)) - `terraform show -json`: Attributes that are declared as using the legacy [Attributes as Blocks](https://www.terraform.io/docs/language/attr-as-blocks.html) behavior are now represented more faithfully in the JSON plan output. ([#29522](https://togithub.com/hashicorp/terraform/issues/29522)) - `terraform init`: Will now update the backend configuration hash value at a more approprimate time, to ensure properly restarting a backend migration process that failed on the first attempt. ([#29860](https://togithub.com/hashicorp/terraform/issues/29860)) - backend/oss: Flatten `assume_role` block arguments, so that they are more compatible with the `terraform_remote_state` data source. ([#29307](https://togithub.com/hashicorp/terraform/issues/29307)) ### [`v1.0.11`](https://togithub.com/hashicorp/terraform/releases/tag/v1.0.11) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.0.10...v1.0.11) ##### 1.0.11 (November 10, 2021) ENHANCEMENTS: - backend/oss: Added support for `sts_endpoint` ([#29841](https://togithub.com/hashicorp/terraform/issues/29841)) BUG FIXES: - config: Fixed </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/ttbud/ttbud).

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [hashicorp/terraform](https://togithub.com/hashicorp/terraform) | minor | `1.1.7` -> `1.3.8` | --- ### Release Notes <details> <summary>hashicorp/terraform</summary> ### [`v1.3.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.7...v1.3.8) #### 1.3.8 (February 09, 2023) BUG FIXES: - Fixed a rare bug causing inaccurate `before_sensitive` / `after_sensitive` annotations in JSON plan output for deeply nested structures. This was only observed in the wild on the rancher/rancher2 provider, and resulted in glitched display in Terraform Cloud's structured plan log view. ([#32543](https://togithub.com/hashicorp/terraform/issues/32543)) - A variable only referenced by an output precondition error_message may be missing during evaluation ([#32464](https://togithub.com/hashicorp/terraform/issues/32464)) - Removing a NestingSingle block from configuration results in an invalid plan ([#32463](https://togithub.com/hashicorp/terraform/issues/32463)) - Null module outputs could be dropped, causing evaluation errors when referring to those module attributes ([#32583](https://togithub.com/hashicorp/terraform/issues/32583)) - Fix terraform crash when applying defaults into a collection with dynamic type constraint. ([#32454](https://togithub.com/hashicorp/terraform/issues/32454)) - Updated to newer github.com/mitchellh/cli version, in turn bringing in updates for several indirect dependencies with known security issues. ([#32609](https://togithub.com/hashicorp/terraform/issues/32609)) - Fix case where the first plan to use a new remote state could be applied twice, corrupting the state ([#32614](https://togithub.com/hashicorp/terraform/issues/32614)) ### [`v1.3.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.6...v1.3.7) #### 1.3.7 (January 04, 2023) BUG FIXES: - Fix exact version constraint parsing for modules using prerelease versions ([#32377](https://togithub.com/hashicorp/terraform/issues/32377)) - Prevent panic when a provider returns a null block value during refresh which is used as configuration via `ignore_changes` ([#32428](https://togithub.com/hashicorp/terraform/issues/32428)) ### [`v1.3.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.5...v1.3.6) #### 1.3.6 (November 30, 2022) BUG FIXES: - Terraform could crash if an orphaned resource instance was deleted externally and had condition checks in the configuration ([#32246](https://togithub.com/hashicorp/terraform/issues/32246)) - Module output changes were being removed and re-added to the stored plan, impacting performance with large numbers of outputs ([#32307](https://togithub.com/hashicorp/terraform/issues/32307)) ### [`v1.3.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.4...v1.3.5) #### 1.3.5 (November 17, 2022) BUG FIXES: - Prevent crash while serializing the plan for an empty destroy operation ([#32207](https://togithub.com/hashicorp/terraform/issues/32207)) - Allow a destroy plan to refresh instances while taking into account that some may no longer exist ([#32208](https://togithub.com/hashicorp/terraform/issues/32208)) - Fix Terraform creating objects that should not exist in variables that specify default attributes in optional objects. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix several Terraform crashes that are caused by HCL creating objects that should not exist in variables that specify default attributes in optional objects within collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Fix inconsistent behaviour in empty vs null collections. ([#32178](https://togithub.com/hashicorp/terraform/issues/32178)) - Prevent file uploads from creating unneeded temporary files when the payload size is known ([#32206](https://togithub.com/hashicorp/terraform/issues/32206)) - Nested attributes marked sensitive by schema no longer reveal sub-attributes in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Nested attributes now more consistently display when they become unknown or null values in the plan diff ([#32004](https://togithub.com/hashicorp/terraform/issues/32004)) - Sensitive values are now always displayed as `(sensitive value)` instead of sometimes as `(sensitive)` \[GH32004] ### [`v1.3.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.3...v1.3.4) #### 1.3.4 (November 02, 2022) BUG FIXES: - Fix invalid refresh-only plan caused by data sources being deferred to apply ([#32111](https://togithub.com/hashicorp/terraform/issues/32111)) - Optimize the handling of condition checks during apply to prevent performance regressions with large numbers of instances ([#32123](https://togithub.com/hashicorp/terraform/issues/32123)) - Output preconditions should not be evaluated during destroy ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Fix crash from `console` when outputs contain preconditions ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Destroy with no state would still attempt to evaluate some values ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - Prevent unnecessary evaluation and planning of resources during the pre-destroy refresh ([#32051](https://togithub.com/hashicorp/terraform/issues/32051)) - AzureRM Backend: support for generic OIDC authentication via the `oidc_token` and `oidc_token_file_path` properties ([#31966](https://togithub.com/hashicorp/terraform/issues/31966)) - Input and Module Variables: Convert variable types before attempting to apply default values. ([#32027](https://togithub.com/hashicorp/terraform/issues/32027)) - When installing remote module packages delivered in tar format, Terraform now limits the tar header block size to 1MiB to avoid unbounded memory usage for maliciously-crafted module packages. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform will now reject excessively-complex regular expression patterns passed to the `regex`, `regexall`, and `replace` functions, to avoid unbounded memory usage for maliciously-crafted patterns. This change should not affect any reasonable patterns intended for practical use. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) - Terraform on Windows now rejects invalid environment variables whose values contain the NUL character when propagating environment variables to a child process such as a provider plugin. Previously Terraform would incorrectly treat that character as a separator between two separate environment variables. ([#32135](https://togithub.com/hashicorp/terraform/issues/32135)) ### [`v1.3.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.2...v1.3.3) #### 1.3.3 (October 19, 2022) BUG FIXES: - Fix error when removing a resource from configuration which has according to the provider has already been deleted. ([#31850](https://togithub.com/hashicorp/terraform/issues/31850)) - Fix error when setting empty collections into variables with collections of nested objects with default values. ([#32033](https://togithub.com/hashicorp/terraform/issues/32033)) ### [`v1.3.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.1...v1.3.2) #### 1.3.2 (October 06, 2022) BUG FIXES: - Fixed a crash caused by Terraform incorrectly re-registering output value preconditions during the apply phase (rather than just reusing the already-planned checks from the plan phase). ([#31890](https://togithub.com/hashicorp/terraform/issues/31890)) - Prevent errors when the provider reports that a deposed instance no longer exists ([#31902](https://togithub.com/hashicorp/terraform/issues/31902)) - Using `ignore_changes = all` could cause persistent diffs with legacy providers ([#31914](https://togithub.com/hashicorp/terraform/issues/31914)) - Fix cycles when resource dependencies cross over between independent provider configurations ([#31917](https://togithub.com/hashicorp/terraform/issues/31917)) - Improve handling of missing resource instances during `import` ([#31878](https://togithub.com/hashicorp/terraform/issues/31878)) ### [`v1.3.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.3.0...v1.3.1) #### 1.3.1 (September 28, 2022) NOTE: - On `darwin/amd64` and `darwin/arm64` architectures, `terraform` binaries are now built with CGO enabled. This should not have any user-facing impact, except in cases where the pure Go DNS resolver causes problems on recent versions of macOS: using CGO may mitigate these issues. Please see the upstream bug [golang/go#52839 for more details. BUG FIXES: - Fixed a crash when using objects with optional attributes and default values in collections, most visible with nested modules. ([#31847](https://togithub.com/hashicorp/terraform/issues/31847)) - Prevent cycles in some situations where a provider depends on resources in the configuration which are participating in planned changes. ([#31857](https://togithub.com/hashicorp/terraform/issues/31857)) - Fixed an error when attempting to destroy a configuration where resources do not exist in the state. ([#31858](https://togithub.com/hashicorp/terraform/issues/31858)) - Data sources which cannot be read during will no longer prevent the state from being serialized. ([#31871](https://togithub.com/hashicorp/terraform/issues/31871)) - Fixed a crash which occured when a resource with a precondition and/or a postcondition appeared inside a module with two or more instances. ([#31860](https://togithub.com/hashicorp/terraform/issues/31860)) ### [`v1.3.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.3.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.9...v1.3.0) #### 1.3.0 (September 21, 2022) NEW FEATURES: - **Optional attributes for object type constraints:** When declaring an input variable whose type constraint includes an object type, you can now declare individual attributes as optional, and specify a default value to use if the caller doesn't set it. For example: ```terraform variable "with_optional_attribute" { type = object({ a = string # a required attribute b = optional(string) # an optional attribute c = optional(number, 127) # an optional attribute with a default value }) } ``` Assigning `{ a = "foo" }` to this variable will result in the value `{ a = "foo", b = null, c = 127 }`. - Added functions: `startswith` and `endswith` allow you to check whether a given string has a specified prefix or suffix. ([#31220](https://togithub.com/hashicorp/terraform/issues/31220)) UPGRADE NOTES: - `terraform show -json`: Output changes now include more detail about the unknown-ness of the planned value. Previously, a planned output would be marked as either fully known or partially unknown, with the `after_unknown` field having value `false` or `true` respectively. Now outputs correctly expose the full structure of unknownness for complex values, allowing consumers of the JSON output format to determine which values in a collection are known only after apply. - `terraform import`: The `-allow-missing-config` has been removed, and at least an empty configuration block must exist to import a resource. - Consumers of the JSON output format expecting on the `after_unknown` field to be only `false` or `true` should be updated to support [the change representation](https://www.terraform.io/internals/json-format#change-representation) described in the documentation, and as was already used for resource changes. ([#31235](https://togithub.com/hashicorp/terraform/issues/31235)) - AzureRM Backend: This release concludes [the deprecation cycle started in Terraform v1.1](https://www.terraform.io/language/upgrade-guides/1-1#preparation-for-removing-azure-ad-graph-support-in-the-azurerm-backend) for the `azurerm` backend's support of "ADAL" authentication. This backend now supports only "MSAL" (Microsoft Graph) authentication. This follows from [Microsoft's own deprecation of Azure AD Graph](https://docs.microsoft.com/en-us/graph/migrate-azure-ad-graph-faq), and so you must follow the migration instructions presented in that Azure documentation to adopt Microsoft Graph and then change your backend configuration to use MSAL authentication before upgrading to Terraform v1.3. - When making requests to HTTPS servers, Terraform will now reject invalid handshakes that have duplicate extensions, as required by RFC 5246 section 7.4.1.4 and RFC 8446 section 4.2. This may cause new errors when interacting with existing buggy or misconfigured TLS servers, but should not affect correct servers. This only applies to requests made directly by Terraform CLI, such as provider installation and remote state storage. Terraform providers are separate programs which decide their own policy for handling of TLS handshakes. - The following backends, which were deprecated in v1.2.3, have now been removed: `artifactory`, `etcd`, `etcdv3`, `manta`, `swift`. The legacy backend name `azure` has also been removed, because the current Azure backend is named `azurerm`. ([#31711](https://togithub.com/hashicorp/terraform/issues/31711)) ENHANCEMENTS: - config: Optional attributes for object type constraints, as described under new features above. ([#31154](https://togithub.com/hashicorp/terraform/issues/31154)) - config: New built-in function `timecmp` allows determining the ordering relationship between two timestamps while taking potentially-different UTC offsets into account. ([#31687](https://togithub.com/hashicorp/terraform/pull/31687)) - config: When reporting an error message related to a function call, Terraform will now include contextual information about the signature of the function that was being called, as an aid to understanding why the call might have failed. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: When reporting an error or warning message that isn't caused by values being unknown or marked as sensitive, Terraform will no longer mention any values having those characteristics in the contextual information presented alongside the error. Terraform will still return this information for the small subset of error messages that are specifically about unknown values or sensitive values being invalid in certain contexts. ([#31299](https://togithub.com/hashicorp/terraform/issues/31299)) - config: `moved` blocks can now describe resources moving to and from modules in separate module packages. ([#31556](https://togithub.com/hashicorp/terraform/issues/31556)) - `terraform fmt` now accepts multiple target paths, allowing formatting of several individual files at once. ([#31687](https://togithub.com/hashicorp/terraform/issues/31687)) - `terraform init`: provider installation errors now mention which host Terraform was downloading from ([#31524](https://togithub.com/hashicorp/terraform/issues/31524)) - CLI: Terraform will report more explicitly when it is proposing to delete an object due to it having moved to a resource instance that is not currently declared in the configuration. ([#31695](https://togithub.com/hashicorp/terraform/issues/31695)) - CLI: When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about pre-plan run tasks ([#31617](https://togithub.com/hashicorp/terraform/issues/31617)) - The AzureRM Backend now only supports MSAL (and Microsoft Graph) and no longer makes use of ADAL (and Azure Active Directory Graph) for authentication ([#31070](https://togithub.com/hashicorp/terraform/issues/31070)) - The COS backend now supports global acceleration. ([#31425](https://togithub.com/hashicorp/terraform/issues/31425)) - provider plugin protocol: The Terraform CLI now calls `PlanResourceChange` for compatible providers when destroying resource instances. ([#31179](https://togithub.com/hashicorp/terraform/issues/31179)) - As an implementation detail of the Terraform Cloud integration, Terraform CLI will now capture and upload [the JSON integration format for state](https://www.terraform.io/internals/json-format#state-representation) along with any newly-recorded state snapshots, which then in turn allows Terraform Cloud to provide that information to API-based external integrations. ([#31698](https://togithub.com/hashicorp/terraform/issues/31698)) BUG FIXES: - config: Terraform was not previously evaluating preconditions and postconditions during the apply phase for resource instances that didn't have any changes pending, which was incorrect because the outcome of a condition can potentially be affected by changes to *other* objects in the configuration. Terraform will now always check the conditions for every resource instance included in a plan during the apply phase, even for resource instances that have "no-op" changes. This means that some failures that would previously have been detected only by a subsequent run will now be detected during the same run that caused them, thereby giving the feedback at the appropriate time. ([#31491](https://togithub.com/hashicorp/terraform/issues/31491)) - `terraform show -json`: Fixed missing markers for unknown values in the encoding of partially unknown tuples and sets. ([#31236](https://togithub.com/hashicorp/terraform/issues/31236)) - `terraform output` CLI help documentation is now more consistent with web-based documentation. ([#29354](https://togithub.com/hashicorp/terraform/issues/29354)) - `terraform init`: Error messages now handle the situation where the underlying HTTP client library does not indicate a hostname for a failed request. ([#31542](https://togithub.com/hashicorp/terraform/issues/31542)) - `terraform init`: Don't panic if a child module contains a resource with a syntactically-invalid resource type name. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - CLI: The representation of destroying already-`null` output values in a destroy plan will no longer report them as being deleted, which avoids reporting the deletion of an output value that was already absent. ([#31471](https://togithub.com/hashicorp/terraform/issues/31471)) - `terraform import`: Better handling of resources or modules that use `for_each`, and situations where data resources are needed to complete the operation. ([#31283](https://togithub.com/hashicorp/terraform/issues/31283)) EXPERIMENTS: - This release concludes the `module_variable_optional_attrs` experiment, which started in Terraform v0.14.0. The final design of the optional attributes feature is similar to the experimental form in the previous releases, but with two major differences: - The `optional` function-like modifier for declaring an optional attribute now accepts an optional second argument for specifying a default value to use when the attribute isn't set by the caller. If not specified, the default value is a null value of the appropriate type as before. - The built-in `defaults` function, previously used to meet the use-case of replacing null values with default values, will not graduate to stable and has been removed. Use the second argument of `optional` inline in your type constraint to declare default values instead. If you have any experimental modules that were participating in this experiment, you will need to remove the experiment opt-in and adopt the new syntax for declaring default values in order to migrate your existing module to the stablized version of this feature. If you are writing a shared module for others to use, we recommend declaring that your module requires Terraform v1.3.0 or later to give specific feedback when using the new feature on older Terraform versions, in place of the previous declaration to use the experimental form of this feature: ```hcl terraform { required_version = ">= 1.3.0" } ``` ### [`v1.2.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.8...v1.2.9) #### 1.2.9 (September 07, 2022) ENHANCEMENTS: - terraform init: add link to documentation when a checksum is missing from the lock file. ([#31726](https://togithub.com/hashicorp/terraform/issues/31726)) ### [`v1.2.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.7...v1.2.8) #### 1.2.8 (August 24, 2022) BUG FIXES: - config: The `flatten` function will no longer panic if given a null value that has been explicitly converted to or implicitly inferred as having a list, set, or tuple type. Previously Terraform would panic in such a situation because it tried to "flatten" the contents of the null value into the result, which is impossible. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) - config: The `tolist`, `toset`, and `tomap` functions, and various automatic conversions that include similar logic, will no longer panic when asked to infer an element type that is convertable from both a tuple type and a list type whose element type is not yet known. ([#31675](https://togithub.com/hashicorp/terraform/issues/31675)) ### [`v1.2.7`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.7) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.6...v1.2.7) #### 1.2.7 (August 10, 2022) ENHANCEMENTS: - config: Check for direct references to deprecated computed attributes. ([#31576](https://togithub.com/hashicorp/terraform/issues/31576)) BUG FIXES: - config: Fix an crash if a submodule contains a resource whose implied provider local name contains invalid characters, by adding additional validation rules to turn it into a real error. ([#31573](https://togithub.com/hashicorp/terraform/issues/31573)) - core: Fix some handling of provider schema attributes which use the newer "structural typing" mechanism introduced with protocol version 6, and therefore with the new Terraform Plugin Framework ([#31532](https://togithub.com/hashicorp/terraform/issues/31532)) - command: Add missing output text for applyable refresh plans. ([#31469](https://togithub.com/hashicorp/terraform/issues/31469)) ### [`v1.2.6`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.6) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.5...v1.2.6) #### 1.2.6 (July 27, 2022) ENHANCEMENTS: - Add a warning and guidance when `terraform init` fails to fully populate the `.terraform.lock.hcl` file. ([#31399](https://togithub.com/hashicorp/terraform/issues/31399)) - Add a direct link to the relevant documentation when `terraform init` fails on missing checksums. ([#31408](https://togithub.com/hashicorp/terraform/issues/31408)) BUG FIXES: - Fix panic on `terraform show` when state file is invalid or unavailable. ([#31444](https://togithub.com/hashicorp/terraform/issues/31444)) - Fix `terraform providers lock` command failing on missing checksums. ([#31389](https://togithub.com/hashicorp/terraform/issues/31389)) - Some combinations of move block operations would be executed in the wrong order ([#31499](https://togithub.com/hashicorp/terraform/issues/31499)) - Don't attribute an error to the provider when a computed attribute is listed in `ignore_changes` ([#31509](https://togithub.com/hashicorp/terraform/issues/31509)) ### [`v1.2.5`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.4...v1.2.5) #### 1.2.5 (July 13, 2022) BUG FIXES: - Report correct error message when a prerelease field is included in the `required_version` global constraint. ([#31331](https://togithub.com/hashicorp/terraform/issues/31331)) - Fix case when extra blank lines were inserted into the plan for unchanged blocks. ([#31330](https://togithub.com/hashicorp/terraform/issues/31330)) ### [`v1.2.4`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.3...v1.2.4) #### 1.2.4 (June 29, 2022) ENHANCEMENTS: - Improved validation of `required_providers` to prevent single providers from being required with multiple names. ([#31218](https://togithub.com/hashicorp/terraform/issues/31218)) - Improved plan performance by optimizing `addrs.Module.String` for allocations. ([#31293](https://togithub.com/hashicorp/terraform/issues/31293)) BUG FIXES: - backend/http: Fixed bug where the HTTP backend would fail to retry acquiring the state lock and ignored the `-lock-timeout` flag. ([#31256](https://togithub.com/hashicorp/terraform/issues/31256)) - Fix crash if a `precondition` or `postcondition` block omitted the required `condition` argument. ([#31290](https://togithub.com/hashicorp/terraform/issues/31290)) ### [`v1.2.3`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.3) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.2...v1.2.3) #### 1.2.3 (June 15, 2022) UPGRADE NOTES: - The following remote state backends are now marked as deprecated, and are planned to be removed in a future Terraform release. These backends have been unmaintained since before Terraform v1.0, and may contain known bugs, outdated packages, or security vulnerabilities. - artifactory - etcd - etcdv3 - manta - swift BUG FIXES: - Missing check for error diagnostics in GetProviderSchema could result in panic ([#31184](https://togithub.com/hashicorp/terraform/issues/31184)) - Module registries returning X-Terraform-Get locations with no URL would error with "no getter available for X-Terraform-Get source protocol" ([#31237](https://togithub.com/hashicorp/terraform/issues/31237)) - Fix crash from concurrent operation on shared set of resource instance dependencies ([#31246](https://togithub.com/hashicorp/terraform/issues/31246)) - backend/cos: `tencentcloud-terraform-lock` tag was not removed in all cases ([#31223](https://togithub.com/hashicorp/terraform/issues/31223)) ### [`v1.2.2`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.2) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.1...v1.2.2) #### 1.2.2 (June 01, 2022) ENHANCEMENTS: - Invalid `-var` arguments with spaces between the name and value now have an improved error message ([#30985](https://togithub.com/hashicorp/terraform/issues/30985)) BUG FIXES: - Terraform now hides invalid input values for sensitive root module variables when generating error diagnostics ([#30552](https://togithub.com/hashicorp/terraform/issues/30552)) - Fixed crash on CLI autocomplete ([#31160](https://togithub.com/hashicorp/terraform/issues/31160)) - The "Configuration contains unknown values" error message now includes attribute paths ([#31111](https://togithub.com/hashicorp/terraform/issues/31111)) ### [`v1.2.1`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.1) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.2.0...v1.2.1) #### 1.2.1 (May 23, 2022) BUG FIXES: - SSH provisioner connections fail when using signed `ed25519` keys ([#31092](https://togithub.com/hashicorp/terraform/issues/31092)) - Crash with invalid module source ([#31060](https://togithub.com/hashicorp/terraform/issues/31060)) - Incorrect "Module is incompatible with count, for_each, and depends_on" error when a provider is nested within a module along with a sub-module using `count` or `for_each` ([#31091](https://togithub.com/hashicorp/terraform/issues/31091)) ### [`v1.2.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.2.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.9...v1.2.0) #### 1.2.0 (May 18, 2022) UPGRADE NOTES: - If you use the [third-party credentials helper plugin terraform-credentials-env](https://togithub.com/apparentlymart/terraform-credentials-env), you should disable it as part of upgrading to Terraform v1.2 because similar functionality is now built in to Terraform itself. The new behavior supports the same environment variable naming scheme but has a difference in priority order from the credentials helper: `TF_TOKEN_...` environment variables will now take priority over credentials blocks in CLI configuration and credentials stored automatically by terraform login, which is not true for credentials provided by any credentials helper plugin. If you see Terraform using different credentials after upgrading, check to make sure you do not specify credentials for the same host in multiple locations. If you use the credentials helper in conjunction with the [hashicorp/tfe](https://registry.terraform.io/providers/hashicorp/tfe) Terraform provider to manage Terraform Cloud or Terraform Enterprise objects with Terraform, you should also upgrade to version 0.31 of that provider, which added the corresponding built-in support for these environment variables. - The official Linux packages for the v1.2 series now require Linux kernel version 2.6.32 or later. - When making outgoing HTTPS or other TLS connections as a client, Terraform now requires the server to support TLS v1.2. TLS v1.0 and v1.1 are no longer supported. Any safely up-to-date server should support TLS 1.2, and mainstream web browsers have required it since 2020. - When making outgoing HTTPS or other TLS connections as a client, Terraform will no longer accept CA certificates signed using the SHA-1 hash function. Publicly trusted Certificate Authorities have not issued SHA-1 certificates since 2015. (Note: the changes to Terraform's requirements when interacting with TLS servers apply only to requests made by Terraform CLI itself, such as provider/module installation and state storage requests. Terraform provider plugins include their own TLS clients which may have different requirements, and may add new requirements in their own releases, independently of Terraform CLI changes.) NEW FEATURES: - `precondition` and `postcondition` check blocks for resources, data sources, and module output values: module authors can now document assumptions and assertions about configuration and state values. If these conditions are not met, Terraform will report a custom error message to the user and halt further execution. - `replace_triggered_by` is a new `lifecycle` argument for managed resources which triggers replacement of an object based on changes to an upstream dependency. - You can now specify credentials for [Terraform-native services](https://www.terraform.io/internals/remote-service-discovery) using an environment variable named as `TF_TOKEN_` followed by an encoded version of the hostname. For example, Terraform will use variable `TF_TOKEN_app_terraform_io` as a bearer token for requests to "app.terraform.io", for the Terraform Cloud integration and private registry requests. ENHANCEMENTS: - When showing a plan, Terraform CLI will now only show "Changes outside of Terraform" if they relate to resources and resource attributes that contributed to the changes Terraform is proposing to make. ([#30486](https://togithub.com/hashicorp/terraform/issues/30486)) - Error messages for preconditions, postconditions, and custom variable validations are now evaluated as expressions, allowing interpolation of relevant values into the output. ([#30613](https://togithub.com/hashicorp/terraform/issues/30613)) - When showing the progress of a remote operation running in Terraform Cloud, Terraform CLI will include information about post-plan [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks). ([#30141](https://togithub.com/hashicorp/terraform/issues/30141)) - Terraform will now show a slightly different note in the plan output if a data resource read is deferred to the apply step due to it depending on a managed resource that has changes pending. ([#30971](https://togithub.com/hashicorp/terraform/issues/30971)) - The "Invalid for_each argument" error message for unknown maps/sets now includes an additional paragraph to try to help the user notice they can move apply-time values into the map *values* instead of the map *keys*, and thus avoid the problem without resorting to `-target`. ([#30327](https://togithub.com/hashicorp/terraform/issues/30327)) - There are some small improvements to the error and warning messages Terraform will emit in the case of invalid provider configuration passing between modules. There are no changes to which situations will produce errors and warnings, but the messages now include additional information intended to clarify what problem Terraform is describing and how to address it. ([#30639](https://togithub.com/hashicorp/terraform/issues/30639)) - The environment variables `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` now serve as fallbacks for the arguments of the same name inside a `cloud` block configuring integration with Terraform Cloud. - The environment variable `TF_WORKSPACE` will now additionally serve as an implicit configuration of a single selected workspace on Terraform Cloud if (and only if) the `cloud` block does not include an explicit workspaces configuration. - The AzureRM Backend now defaults to using MSAL (and Microsoft Graph) rather than ADAL (and Azure Active Directory Graph) for authentication. ([#30891](https://togithub.com/hashicorp/terraform/issues/30891)) - The AzureRM Backend now supports authenticating as a service principal using OpenID Connect. ([#30936](https://togithub.com/hashicorp/terraform/pull/30936)) - When running on macOS, Terraform will now use platform APIs to validate certificates presented by TLS (HTTPS) servers. This may change exactly which root certificates Terraform will accept as valid. ([#30768](https://togithub.com/hashicorp/terraform/issues/30768)) - Show remote host in error message for clarity when installation of provider fails ([#30810](https://togithub.com/hashicorp/terraform/issues/30810)) - Terraform now prints a warning when adding an attribute to `ignore_changes` that is managed only by the provider. Specifying non-configurable attributes in `ignore_changes` has no effect because `ignore_changes` tells Terraform to ignore future changes made in the configuration. ([#30517](https://togithub.com/hashicorp/terraform/issues/30517)) - `terraform show -json` now includes exact type information for output values. ([#30945](https://togithub.com/hashicorp/terraform/issues/30945)) - The `ssh` provisioner connection now supports SSH over HTTP proxy. ([#30274](https://togithub.com/hashicorp/terraform/pull/30274)) - - The SSH client for provisioners now supports newer key algorithms, allowing it to connect to servers running more recent versions of OpenSSH. ([#30962](https://togithub.com/hashicorp/terraform/issues/30962)) BUG FIXES: - Terraform now handles type constraints, nullability, and custom variable validation properly for root module variables. Previously there was an order of operations problem where the nullability and custom variable validation were checked too early, prior to dealing with the type constraints, and thus that logic could potentially "see" an incorrectly-typed value in spite of the type constraint, leading to incorrect errors. ([#29959](https://togithub.com/hashicorp/terraform/issues/29959)) - When reporting a type mismatch between the true and false results of a conditional expression when both results are of the same structural type kind (object/tuple, or a collection thereof), Terraform will no longer return a confusing message like "the types are object and object, respectively", and will instead attempt to explain how the two structural types differ. ([#30920](https://togithub.com/hashicorp/terraform/issues/30920)) - Applying the various type conversion functions like `tostring`, `tonumber`, etc to `null` will now return a null value of the intended type. For example, `tostring(null)` converts from a null value of an unknown type to a null value of string type. Terraform can often handle such conversions automatically when needed, but explicit annotations like this can help Terraform to understand author intent when inferring type conversions for complex-typed values. ([#30879](https://togithub.com/hashicorp/terraform/issues/30879)) - Terraform now returns an error when `cidrnetmask()` is called with an IPv6 address, as it was previously documented to do. IPv6 standards do not preserve the "netmask" syntax sometimes used for IPv4 network configuration; use CIDR prefix syntax instead. ([#30703](https://togithub.com/hashicorp/terraform/issues/30703)) - When performing advanced state management with the `terraform state` commands, Terraform now checks the `required_version` field in the configuration before proceeding. ([#30511](https://togithub.com/hashicorp/terraform/pull/30511)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will now prioritize local terraform variables over remote terraform variables in operations such as `import`, `plan`, `refresh` and `apply` for workspaces in local execution mode. This behavior applies to both `remote` backend and the `cloud` integration configuration. ([#29972](https://togithub.com/hashicorp/terraform/issues/29972)) - `terraform show -json`: JSON plan output now correctly maps aliased providers to their configurations, and includes the full provider source address alongside the short provider name. ([#30138](https://togithub.com/hashicorp/terraform/issues/30138)) - The local token configuration in the `cloud` and `remote` backend now has higher priority than a token specified in a `credentials` block in the CLI configuration. ([#30664](https://togithub.com/hashicorp/terraform/issues/30664)) - The `cloud` integration now gracefully exits when `-input=false` and an operation requires some user input. - Terraform will now reliably detect an inteerruptiong (e.g. Ctrl+C) during planning for `terraform apply -auto-approve`. Previously there was a window of time where interruption would cancel the plan step but not prevent Terraform from proceeding to the apply step. ([#30979](https://togithub.com/hashicorp/terraform/issues/30979)) - Terraform will no longer crash if a provider fails to return a schema. ([#30987](https://togithub.com/hashicorp/terraform/issues/30987)) ### [`v1.1.9`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.9) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.8...v1.1.9) #### 1.1.9 (April 20, 2022) BUG FIXES: - cli: Fix crash when using sensitive values in sets. ([#30825](https://togithub.com/hashicorp/terraform/issues/30825)) - cli: Fix double-quoted map keys when rendering a diff. ([#30855](https://togithub.com/hashicorp/terraform/issues/30855)) - core: Prevent errors when handling a data source with incompatible schema changes ([#30830](https://togithub.com/hashicorp/terraform/issues/30830)) ENHANCEMENTS: - cli: Terraform now supports [run tasks](https://www.terraform.io/cloud-docs/workspaces/settings/run-tasks), a Terraform Cloud integration for executing remote operations, for the post plan stage of a run. ### [`v1.1.8`](https://togithub.com/hashicorp/terraform/releases/tag/v1.1.8) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.1.7...v1.1.8) #### 1.1.8 (April 07, 2022) BUG FIXES: - cli: Fix missing identifying attributes (e.g. "id", "name") when displaying plan diffs with nested objects. ([#30685](https://togithub.com/hashicorp/terraform/issues/30685)) - functions: Fix error when `sum()` function is called with a collection of string-encoded numbers, such as `sum(["1", "2", "3"])`. ([#30684](https://togithub.com/hashicorp/terraform/issues/30684)) - When rendering a diff, Terraform now quotes the name of any object attribute whose string representation is not a valid identifier. ([#30766](https://togithub.com/hashicorp/terraform/issues/30766)) - Terraform will no longer crash in the `terraform apply` phase if an error occurs during backend configuration. ([#30780](https://togithub.com/hashicorp/terraform/pull/30780)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate).  Co-authored-by: Renovate Bot <renovate@whitesourcesoftware.com>

golang/go#52839

zyxkad · 2023-09-14T02:32:08Z

I'm using mac M1 Ventura 13.5 (22G74), the local dns issue is actually affected my nslookup command, but it didn't affect the go program you provide with whether CGO enabled or not.

$ go version
go version go1.20.4 darwin/arm64

go env

GO111MODULE=""
GOARCH="arm64"
GOBIN="/Users/ckpn/Mine/projects/golang/bin"
GOCACHE="/Users/ckpn/Library/Caches/go-build"
GOENV="/Users/ckpn/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/ckpn/Mine/projects/golang/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/ckpn/Mine/projects/golang"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/homebrew/Cellar/go/1.20.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.20.4/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.4"
GCCGO="gccgo"
AR="ar"
CC="cc"
CXX="c++"
CGO_ENABLED="0"
GOMOD="/Users/ckpn/Mine/projects/golang/test/dns/go.mod"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3g/rxdhvbj96lv68y35t2cvghkr0000gn/T/go-build2449011362=/tmp/go-build -gno-record-gcc-switches -fno-common"

lukasmalkmus · 2024-04-09T10:38:11Z

I'm seeing the same behaviour: go version go1.22.2 darwin/arm64!

heschi added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 11, 2022

heschi added this to the Backlog milestone May 11, 2022

mattrobenolt changed the title ~~net: pure Go DNS resolver hangs with ipv6 link-local address~~ net: pure Go DNS resolver hangs with ipv6 link-local address on macOS May 11, 2022

dbussink mentioned this issue Jun 29, 2022

Release MacOS with CGO enabled planetscale/cli#523

Merged

kmoe mentioned this issue Sep 5, 2022

terraform init/apply kills Macbook Pro M1 Network connection #349 hashicorp/terraform#31467

Open

apparentlymart mentioned this issue Sep 21, 2022

net: Support the /etc/resolver DNS resolution configuration hierarchy on OS X when cgo is disabled #12524

Closed

This comment was marked as off-topic.

Sign in to view

pacorreia mentioned this issue Oct 4, 2022

Terraform 1.3.1 (and 1.3.0) forcing and failing DNS resolution on IPv6 hashicorp/terraform#31935

Closed

This comment was marked as off-topic.

Sign in to view

This was referenced Oct 12, 2022

Kubectl on MacOS Montery 12.6 causing networking crash, requires restart kubernetes/kubectl#1299

Closed

Kubernetes cluster unreachable -> dial tcp: i/o timeout helm/helm#11306

Closed

glours added a commit to glours/compose that referenced this issue Oct 19, 2022

use CGO_ENABLED to avoid full system crash for mac users with a IPV6 …

3f8d2ab

…config see this issue golang/go#52839 Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>

glours mentioned this issue Oct 19, 2022

use CGO_ENABLED to avoid full system crash for mac users with a IPV6 config docker/compose#9932

Closed

glours added a commit to glours/compose that referenced this issue Oct 19, 2022

use CGO_ENABLED to avoid full system crash for mac users with a IPV6 …

d9397cf

…config see this issue golang/go#52839 Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>

glours added a commit to glours/compose that referenced this issue Oct 19, 2022

use CGO_ENABLED to avoid full system crash for mac users with a IPV6 …

579a33f

…config see this issue golang/go#52839 Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>

glours added a commit to glours/compose that referenced this issue Oct 24, 2022

use CGO_ENABLED to avoid full system crash for mac users with a IPV6 …

42ded95

…config see this issue golang/go#52839 Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>

jhump mentioned this issue Jan 23, 2023

buf curl stuck for 10 seconds on "Dialing (tcp)" bufbuild/buf#1745

Closed

PeterSchafer added a commit to snyk/cli that referenced this issue Mar 28, 2023

fix: enable cgo to fix macos network issues

6aec5ff

golang/go#52839

jakolehm mentioned this issue Aug 18, 2023

Internet connection stops working when using Lens lensapp/lens#6063

Open

dmitshur added the OS-Darwin label Apr 9, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839

net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839

mattrobenolt commented May 10, 2022

heschi commented May 11, 2022

dannyfallon commented Aug 11, 2022

apparentlymart commented Sep 6, 2022

silvestriluca commented Sep 13, 2022 •

edited

heschi commented Sep 13, 2022

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

zyxkad commented Sep 14, 2023 •

edited

lukasmalkmus commented Apr 9, 2024

net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839

net: pure Go DNS resolver hangs with ipv6 link-local address on macOS #52839

Comments

mattrobenolt commented May 10, 2022

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

What operating system and processor architecture are you using (go env)?

What did you do?

What did you expect to see?

What did you see instead?

heschi commented May 11, 2022

dannyfallon commented Aug 11, 2022

apparentlymart commented Sep 6, 2022

silvestriluca commented Sep 13, 2022 • edited

heschi commented Sep 13, 2022

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

zyxkad commented Sep 14, 2023 • edited

lukasmalkmus commented Apr 9, 2024

What version of Go are you using (`go version`)?

What operating system and processor architecture are you using (`go env`)?

silvestriluca commented Sep 13, 2022 •

edited

zyxkad commented Sep 14, 2023 •

edited