macOS
Homebrewverified · 100%
brew install tfmigrateprovider-native install command
brew / rank 1911
Install tfmigrate with Homebrew
Terraform/OpenTofu state migration tool for GitOps. Version 0.4.5 via Homebrew; verified 2026-07-26.
install
Additional install commands
overview
Package summary
Terraform/OpenTofu state migration tool for GitOps
Project links
Commands and aliases
- tfmigrate
history
Project history and usage
tfmigrate is a Terraform and OpenTofu state migration tool for GitOps. Its README frames Terraform state operations as code: write state moves, removals, imports, and related operations in HCL, review them in git, then plan and apply them in sequence.
Project history
The project was created to address a common production Terraform problem: state manipulations are unavoidable during refactoring, but raw `terraform state` commands are error-prone and do not fit well into pull-request and CI/CD workflows. tfmigrate's README explicitly argues that state operations should be committed to git.
The tool wraps Terraform or OpenTofu under the hood rather than reimplementing their state mechanics. It supports dry-run planning with temporary local state, migration history, local/S3/GCS storage for applied migration records, monorepo-style state splits and merges, and migration files written as HCL.
Recent release notes show continuing maintenance for the changing Terraform ecosystem, including support for OpenTofu versions, Terraform 1.11 through 1.15, Terragrunt CLI redesign handling, configurable environment injection into `.tfmigrate.hcl`, and GitHub Actions and Go toolchain updates.
Adoption history
The repository shows more than a thousand GitHub stars and is packaged by Homebrew, MacPorts, and Nix in the input metadata. That adoption profile fits a tool used by infrastructure teams with long-lived Terraform states and CI-based review.
tfmigrate's appeal is strongest for teams that already use GitOps: it lets state migrations travel with the configuration change they support, instead of being performed manually before or after a merge.
How it is used
The documented workflow is to write a migration file such as `state_mv.hcl`, run `tfmigrate plan` to verify the state operation against Terraform plan output without updating remote state, and then run `tfmigrate apply` to push the migrated state when the plan is clean.
tfmigrate can invoke `terraform`, `tofu`, or Terragrunt via `TFMIGRATE_EXEC_PATH`, and the README recommends trying the included sandbox before using the tool on production state.
Why package nerds care
tfmigrate is important in package metadata because it solves a lifecycle problem that plain Terraform intentionally leaves low-level. It turns one-off state surgery into reviewable, repeatable migration files.
As a package-manager tool, it is most useful when installed in CI images and developer machines beside Terraform/OpenTofu, making the same state migration command available during local rehearsal and automated review.
Timeline
- 2025: v0.4.2 release notes add OpenTofu 1.9, Terraform 1.11, Terragrunt CLI redesign handling, and environment injection into `.tfmigrate.hcl`.
- 2025: v0.4.3 release notes add OpenTofu 1.10 and Terraform 1.12 support.
- 2025: v0.4.4 release notes add OpenTofu 1.11 and Terraform 1.14 support.
- 2026: v0.4.5 is listed as the latest release and includes Terraform 1.15 support.
Related projects
- Terraform and OpenTofu are the execution engines tfmigrate invokes.
- Terragrunt is supported through `TFMIGRATE_EXEC_PATH` with version-specific guidance.
- Digger is mentioned in recent release notes as an integration example.
Sources
- https://github.com/minamijoyo/tfmigrate
- https://github.com/minamijoyo/tfmigrate/releases
- source_facts.package-manager
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
.tfmigrate.hcl
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
tfmigrate | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version0.4.5
manager updated2026-07-26
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:tfmigrate |
|---|---|
| Version | 0.4.5 |
| Package manager | Homebrew |
| Homepage | https://github.com/minamijoyo/tfmigrate |
| Repository | https://github.com/minamijoyo/tfmigrate |
| Last updated | 2026-07-26T00:50:39+02:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation