Sync State File to appStack
The tfstate to appStack feature is a CLI-based automation for importing Terraform state files (.tfstate) into StackGen, making it easier to keep your infrastructure state in sync and continuously compliant.
Instead of manually uploading state files or managing versions through the StackGen User Interface, you can now run a single CLI command to import a state file and either create a new appStack or a new version of an existing appStack. This streamlines your workflow, supports CI/CD integration, and reduces the risk of human error in critical infrastructure processes.
Often, your team uses StackGen in an iterative workflow to ensure infrastructure compliance. A typical process involves:
- Importing the initial state file (
.tfstatev1) into StackGen, making changes to the same, and deploying it. - After subsequent infrastructure updates, deploy it again and re-import the updated state (
.tfstatev2) to validate compliance and identify security risks.
To streamline this process, you can use the StackGen CLI to automate the import of your .tfstate file. You can now:
This will reduce manual overhead and enable tighter CI/CD integrations, and your:
- Infrastructure team can run a script that automatically runs
stackgen import stateto sync the updated state into StackGen after aterraform apply. - Security and DevOps teams can then review changes, validate compliance, and push new versions.
Example: After provisioning a new environment using Terraform, the state file is automatically pushed to StackGen so that you can:
- Create a new AppStack version.
- Trigger compliance scans.
- Review diffs between previous and current states.
Key Benefits
- Increased Efficiency: Reduces manual steps in syncing
.tfstatefile with StackGen. - Improved Security: Enables real-time compliance checks after every infrastructure change.
- CI/CD Integration: Facilitates continuous compliance by embedding StackGen into DevOps workflows.
- Ease of use: Eliminates friction in recurring workflows.