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
Describe the bug
Currently, the terraform backend only supports *.tf files. There are a lot of situations where other file types are necessary, such as when keeping configuration for some system in a .json or some other format, which is then read by the Terraform module.
I think it would be good to relax this constraint to support any and all filetypes, but keep the default to *.tf as to not have undesired consequences.
Pants version
2.21.0.rc0
OS
Linux
Additional info
n/a
The text was updated successfully, but these errors were encountered:
Closespantsbuild#21506.
It's pretty common to want to include other types of files in a
Terraform module (such as json configuration, sql files and such) and
use them from Terraform by loading them via `file`.
Some examples from the repository I'm currently working on are: .json,
.sql, .zed (SpiceDB schema), so I think it makes sense to allow for any
file extensions here.
frekw
linked a pull request
Oct 8, 2024
that will
close
this issue
This is similar to other backends work, where the SourcesField subclass will pull in only the files that are in that language, and other files are pulled in with resources or files
Describe the bug
Currently, the terraform backend only supports
*.tf
files. There are a lot of situations where other file types are necessary, such as when keeping configuration for some system in a.json
or some other format, which is then read by the Terraform module.I think it would be good to relax this constraint to support any and all filetypes, but keep the default to
*.tf
as to not have undesired consequences.Pants version
2.21.0.rc0
OS
Linux
Additional info
n/a
The text was updated successfully, but these errors were encountered: