You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform should have informed the user not to end paths with /
Actual Behavior
Terraform stored the state in the path with /. Consul recognises this as a directory and refuses to show the content.
Terraform had problems with the state locking when there was a trailing /
Steps to Reproduce
Put a trailing / in your consul backend path and apply. The lock issue can already been seen during init.
terraform apply
Important Factoids
Terraform had issues migrating from the path with / to one without /.
It also had problems migrating from a file state to the consul backend with /.
To achieve each, I deleted all state files and initialised from scratch.
The text was updated successfully, but these errors were encountered:
When the path ends with / (e.g. `path = "tfstate/"), the lock
path used will contain two consecutive slashes (e.g. `tfstate//.lock`) which
Consul does not accept.
This change the lock path so it is sanitized to `tfstate/.lock`.
If the user has two different Terraform project, one with `path = "tfstate"` and
the other with `path = "tfstate/"`, the paths for the locks will be the same
which will be confusing as locking one project will lock both. I wish it were
possible to forbid ending slashes altogether but doing so would require all
users currently having an ending slash in the path to manually move their
Terraform state and would be a poor user experience.
Closeshashicorp#15747
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked as resolved and limited conversation to collaborators
Oct 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform v0.10.0
Terraform Configuration Files
Expected Behavior
Terraform should have informed the user not to end paths with /
Actual Behavior
Terraform stored the state in the path with /. Consul recognises this as a directory and refuses to show the content.
Terraform had problems with the state locking when there was a trailing /
Steps to Reproduce
Put a trailing / in your consul backend path and apply. The lock issue can already been seen during init.
terraform apply
Important Factoids
Terraform had issues migrating from the path with / to one without /.
It also had problems migrating from a file state to the consul backend with /.
To achieve each, I deleted all state files and initialised from scratch.
The text was updated successfully, but these errors were encountered: