Use os.CreateTemp to create a temporary file in the target directory, then do an atomic rename once you’ve finished writing.

Here’s an interesting function from the Tailscale repos that Anton told me about in a code review last week: a function to write to a file atomically. This ensures you don’t get partially written data in the final file.

10import (
11	"fmt"
12	"os"
13	"path/filepath"
14	"runtime"
15)
16
17// WriteFile writes data to filename+some suffix, then renames it into filename.
18// The perm argument is ignored on Windows, but if the target filename already
19// exists then the target file's attributes and ACLs are preserved. If the target
20// filename already exists but is not a regular file, WriteFile returns an error.
21func WriteFile(filename string, data []byte, perm os.FileMode) (err error) {
22	fi, err := os.Stat(filename)
23	if err == nil && !fi.Mode().IsRegular() {
24		return fmt.Errorf("%s already exists and is not a regular file", filename)
25	}
26	f, err := os.CreateTemp(filepath.Dir(filename), filepath.Base(filename)+".tmp")
27	if err != nil {
28		return err
29	}
30	tmpName := f.Name()
31	defer func() {
32		if err != nil {
33			f.Close()
34			os.Remove(tmpName)
35		}
36	}()
37	if _, err := f.Write(data); err != nil {
38		return err
39	}
40	if runtime.GOOS != "windows" {
41		if err := f.Chmod(perm); err != nil {
42			return err
43		}
44	}
45	if err := f.Sync(); err != nil {
46		return err
47	}
48	if err := f.Close(); err != nil {
49		return err
50	}
51	return Rename(tmpName, filename)
52}

This is similar to code I’ve produced in other projects to do atomic file writes – write to a temporary file first, then do an atomic rename to the final destination.

The temporary file is created in the same directory as the target, to give the best chance of being able to do an atomic rename. You can’t do an atomic rename across filesystem boundaries; using the same directory ensures both files are on the same filesystem.

To handle concurrent writes, I normally insert a random UUID into the temporary filename, so different processes write to different tempfiles. This is handled automatically by Go’s os.CreateTemp function, which adds a random string to the end of the filename.

The Rename() function has different logic for Windows and non-Windows systems:

• On non-Windows, it uses os.Rename(). The Go documentation notes that “even within the same directory, on non-Unix platforms Rename is not an atomic operation”.
• On Windows, it makes a syscall to the ReplaceFileW function. A cursory Internet search is conflicted on whether this is a truly atomic rename, although concurs that it’s the best option on Windows.