Autoschematic

State drift means the real remote object changed without the repo being updated to match. In Autoschematic, that does not force you to immediately push your old file back onto the system. Very often, the better first move is to pull the real state into git, review it, and then make the change you actually intended from that updated baseline.

For a quick yes-or-no check on a single resource file, use check-drift:

autoschematic check-drift --path main/aws/iam/roles/support.ron

This command exits successfully when the file matches remote state and exits non-zero when it has drifted. This is intended for scripts, tooling, and quick checks.

If you use Visual Studio Code, the extension makes this especially pleasant:

Right-click on a file and Autoschematic: Compare with remote will fetch the remote state and show a clean diff.

• Pull Remote State writes the live remote version back into the file.