# Install tfautomv with Homebrew, Nix

Generate Terraform moved blocks automatically for painless refactoring. Version 0.7.0 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#tfautomv.

## Install

```sh
sudo av install brew:tfautomv
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install tfautomv
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#tfautomv
```

  Evidence: nixpkgs package indexes: pkgs/by-name/tf/tfautomv/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:tfautomv
- **Package manager:** Homebrew
- **Version:** 0.7.0
- **Source summary:** Generate Terraform moved blocks automatically for painless refactoring
- **Homepage:** <https://github.com/busser/tfautomv>
- **Repository:** <https://github.com/busser/tfautomv>
- **Last updated:** 2026-07-26T00:50:38+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- tfautomv (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.7.0
## Project history and usage

tfautomv is a Terraform and OpenTofu refactoring assistant that detects create/delete pairs in plans and generates `moved` blocks or `terraform state mv` commands. Its purpose is to preserve state when resources are renamed or moved in code.

### Project history

The project started in April 2022 with design documentation, followed by a July 2022 MVP and v0.1.0 tag. The README now marks the tool stable and used in production, with maintenance mostly limited to dependency updates and bug reports.

The tool grew from generating Terraform moved blocks into supporting state move commands, cross-directory moves, OpenTofu through `--terraform-bin`, preplanned files, verbosity for unmatched resources, and ignore rules for provider quirks.

### Adoption history

The README documents Homebrew, a shell installer, Arch/Yay, asdf, releases, and source builds. The package input also records Homebrew and Nix availability, matching the tool's Unix-centric target audience.

### How it is used

Users run `tfautomv` in a Terraform working directory after a pure refactor. The tool runs or reads a plan, identifies likely state-preserving moves, writes `moves.tf`, or emits shell commands for `terraform state mv` review and execution.

The official workflow recommends separating structural refactors from configuration changes, running tfautomv, applying the generated moves until the plan shows no infrastructure changes, and then making attribute changes separately.

### Why package nerds care

tfautomv is significant to Terraform package users because it automates a formerly manual refactoring chore. It also tracks the post-Terraform-fork ecosystem by explicitly supporting OpenTofu while retaining Terraform-compatible command semantics.

### Timeline

- 2022-04-16: First design commit
- 2022-07-14: MVP implementation commit
- 2022-07-15: v0.1.0 tag
- 2023-11-15: v0.5.4 tag
- 2024-02-13: v0.6.0 tag
- 2025-06-06: v0.7.0 tag

### Related projects

- Terraform supplies plan/state semantics and the moved-block syntax.
- OpenTofu is supported through the `--terraform-bin` flag.
- Terragrunt is discussed as a wrapper-script integration rather than a direct binary replacement.

### Sources

- Official git tags and commit history from https://github.com/busser/tfautomv
- <https://github.com/busser/tfautomv/blob/main/README.md>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Other Package-Manager Records

- Nix - tfautomv: normalized package name match | nixpkgs package indexes: pkgs/by-name/tf/tfautomv/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/tfautomv.yml](https://github.com/mxcl/pkgdb/blob/main/combined/tfautomv.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph