Fix: Isolate Terraform state per module so both can be deployed at the same time#105
Open
tyagidevansh wants to merge 1 commit into
Open
Fix: Isolate Terraform state per module so both can be deployed at the same time#105tyagidevansh wants to merge 1 commit into
tyagidevansh wants to merge 1 commit into
Conversation
ataylor14
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both modules shared one Terraform state bucket (do-not-delete-awsgoat-state-files-<ACCOUNT_ID>) and one state key (terraform.tfstate).
As a result:
Error: no schema available ... while reading state; this is a bug in Terraform.Nowhere in the Readme is it mentioned that both modules cannot be run at the same time. It is not a stretch to think that many users would try to run both modules at the same time, and would notice Terraform apply failing. Though this does not make the project completely unusable, I think the ability to deploy both at the same time should be present.