Setup Terraform state migration tooling

[BigBen-7]

Description

Tools for safely migrating Terraform state between backends.

Requirements

• State migration scripts
• Pre-migration validation
• Rollback procedure
• State backup automation
• Migration documentation

Files to Touch

• infrastructure/scripts/migrate-state.sh
• infrastructure/scripts/validate-state.sh
• infrastructure/docs/state-migration.md

Complexity: 250 points

[anilyagiz]

Hi, I’d like to apply for this issue.

I have around 5 years of experience as a software developer, with hands-on experience in infrastructure automation, CI/CD workflows, shell scripting, deployment tooling, Terraform-based infrastructure management, and production reliability. I have worked on systems where safe infrastructure changes, reproducible deployment processes, state consistency, and rollback planning were important to reduce operational risk.

For this issue, I would start by reviewing the current Terraform backend configuration, state layout, workspaces, and any existing scripts around infrastructure management. Since Terraform state is critical and sensitive, I would focus on building migration tooling that is safe by default and validates each step before making changes.

I would implement infrastructure/scripts/validate-state.sh to perform pre-migration checks, including verifying Terraform initialization, backend connectivity, workspace selection, state accessibility, provider compatibility, lock status, and whether the current state matches the expected infrastructure configuration. I would also include checks to detect obvious drift or configuration issues before migration begins.

For the migration flow, I would implement infrastructure/scripts/migrate-state.sh with a clear step-by-step process for safely moving state between backends. The script would create a timestamped backup before migration, verify the backup is readable, run the migration using Terraform’s supported state/backend migration flow, and validate the migrated state afterward. I would make sure the script avoids destructive behavior and requires explicit confirmation for risky actions.

Rollback would be a core part of the implementation. I would document and support a rollback procedure that allows the team to restore from the latest known-good state backup if migration validation fails. The tooling would preserve backups in a predictable location and include enough metadata to identify the source backend, target backend, workspace, timestamp, and migration result.

I would also update infrastructure/docs/state-migration.md with a clear migration runbook, including prerequisites, required environment variables, validation steps, backup behavior, rollback process, troubleshooting guidance, and examples for common backend migration scenarios.

Finally, I would add tests or dry-run support where practical, so maintainers can verify the scripts before performing an actual migration. My goal would be to deliver safe, transparent, and maintainable Terraform state migration tooling that helps PinSpace move state between backends without risking accidental state loss or deployment instability.

[omonxooo-commits]

@omonxooo-commits has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this project. I promise to deliver

ℹ️ Repo Maintainers: To accept this application, review their application or assign @omonxooo-commits to this issue.

[portableDD]

@portableDD has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

can i handle this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @portableDD to this issue.

[Oluwasuyi-Timilehin]

@Oluwasuyi-Timilehin has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, please assign me to this task. I would resolve it immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Timilehin to this issue.

[Glam26]

@Glam26 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to take this on.

I've worked on similar enhancements involving backend services, frontend features, and testing. I'll deliver a solution that aligns with the existing codebase, includes thorough test coverage, and is accompanied by clear documentation where necessary.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Glam26 to this issue.

[grantfox-oss]

🦊 GrantFox — @portableDD has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #705)
2. Your PR will be reviewed by the PinSpace-Org maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @portableDD! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @portableDD: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@portableDD's PR #830 was approved and merged by @BigBen-7.

🏆 @portableDD: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (506 total points). Track your full progress on GrantFox.

👏 Great work, @portableDD! Keep contributing to PinSpace-Org.

[drips-wave]

This issue has been completed by @portableDD as part of the Stellar Wave Program's 6th Wave 🥳

😎 @portableDD: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.