Sanitize lock path for the Consul backend when it ends with a / #25842
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.
When the path ends with / (e.g.
path = "tfstate/"), the lock path used will contain two consecutive slashes (e.g.
tfstate//.lock`) whichConsul 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"
andthe other with
path = "tfstate/"
, the paths for the locks will be the samewhich 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.
Closes #15747