Upgrade to Go 1.17
This includes the addition of the new "//go:build" comment form in addition
to the legacy "// +build" notation, as produced by gofmt to ensure
consistent behavior between Go versions. The new directives are all
equivalent to what was present before, so there's no change in behavior.
Go 1.17 continues to use the Unicode 13 tables as in Go 1.16, so this
upgrade does not require also upgrading our Unicode-related dependencies.
This upgrade includes the following breaking changes which will also
appear as breaking changes for Terraform users, but that are consistent
with the Terraform v1.0 compatibility promises.
- On MacOS, Terraform now requires macOS 10.13 High Sierra or later.
This upgrade also includes the following breaking changes which will
appear as breaking changes for Terraform users that are inconsistent with
our compatibility promises, but have justified exceptions as follows:
- cidrsubnet, cidrhost, and cidrnetmask will now reject IPv4 CIDR
addresses whose decimal components have leading zeros, where previously
they would just silently ignore those leading zeros.
This is a security-motivated exception to our compatibility promises,
because some external systems interpret zero-prefixed octets as octal
numbers rather than decimal, and thus the previous lenient parsing could
lead to a different interpretation of the address between systems, and
thus potentially allow bypassing policy when configuring firewall rules
etc.
This upgrade also includes the following breaking changes which could
_potentially_ appear as breaking changes for Terraform users, but that do
not in practice for the reasons given:
- The Go net/url package no longer allows query strings with pairs
separated by semicolons instead of ampersands. This primarily affects
HTTP servers written in Go, and Terraform includes a special temporary
HTTP server as part of its implementation of OAuth for "terraform login",
but that server only needs to accept URLs created by Terraform itself
and Terraform does not generate any URLs that would be rejected.
2021-08-17 02:19:17 +02:00
|
|
|
//go:build windows
|
2020-10-13 02:15:42 +02:00
|
|
|
// +build windows
|
|
|
|
|
|
|
|
package replacefile
|
|
|
|
|
|
|
|
import (
|
|
|
|
"os"
|
|
|
|
"syscall"
|
|
|
|
|
|
|
|
"golang.org/x/sys/windows"
|
|
|
|
)
|
|
|
|
|
|
|
|
// AtomicRename renames from the source path to the destination path,
|
|
|
|
// atomically replacing any file that might already exist at the destination.
|
|
|
|
//
|
|
|
|
// Typically this operation can succeed only if the source and destination
|
|
|
|
// are within the same physical filesystem, so this function is best reserved
|
|
|
|
// for cases where the source and destination exist in the same directory and
|
|
|
|
// only the local filename differs between them.
|
|
|
|
func AtomicRename(source, destination string) error {
|
|
|
|
// On Windows, renaming one file over another is not atomic and certain
|
|
|
|
// error conditions can result in having only the source file and nothing
|
|
|
|
// at the destination file. Instead, we need to call into the MoveFileEx
|
|
|
|
// Windows API function, setting two flags to opt in to replacing an
|
|
|
|
// existing file.
|
|
|
|
srcPtr, err := syscall.UTF16PtrFromString(source)
|
|
|
|
if err != nil {
|
|
|
|
return &os.LinkError{"replace", source, destination, err}
|
|
|
|
}
|
|
|
|
destPtr, err := syscall.UTF16PtrFromString(destination)
|
|
|
|
if err != nil {
|
|
|
|
return &os.LinkError{"replace", source, destination, err}
|
|
|
|
}
|
|
|
|
|
|
|
|
flags := uint32(windows.MOVEFILE_REPLACE_EXISTING | windows.MOVEFILE_WRITE_THROUGH)
|
|
|
|
err = windows.MoveFileEx(srcPtr, destPtr, flags)
|
|
|
|
if err != nil {
|
|
|
|
return &os.LinkError{"replace", source, destination, err}
|
|
|
|
}
|
|
|
|
return nil
|
|
|
|
}
|