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
The path separator in .terraformignore file is dependant on the host OS. For example, while running on windows, the paths in .terraformignore need to be separated of the foo\bar syntax and won't work if they are in the foo/bar syntax.
For repos with both windows and linux based engineers, this is causing us to add both windows and linux patterns to the .terraformignore file which we'd like to avoid.
Below test case demonstrates the issue. Also note that the terraformignore_test.go that comes in this repo fails when run on windows.
I'd be surprised if this is the intended behavior. One would expect the patterns to be always linux based (forward slash) irrespective of the runtime OS. But, removing support for baskslash patterns at this point would be a breaking change.
I'm happy to attempt a PR for a fix if I can get an agreement.
The path separator in
.terraformignore
file is dependant on the host OS. For example, while running on windows, the paths in.terraformignore
need to be separated of thefoo\bar
syntax and won't work if they are in thefoo/bar
syntax.For repos with both windows and linux based engineers, this is causing us to add both windows and linux patterns to the
.terraformignore
file which we'd like to avoid.Below test case demonstrates the issue. Also note that the
terraformignore_test.go
that comes in this repo fails when run on windows.I'd be surprised if this is the intended behavior. One would expect the patterns to be always linux based (forward slash) irrespective of the runtime OS. But, removing support for baskslash patterns at this point would be a breaking change.
I'm happy to attempt a PR for a fix if I can get an agreement.
The text was updated successfully, but these errors were encountered: