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
Allow .yml file extenstion for tfaction and tfaction-root config files
Why is the feature needed?
YAML files can have .yml or .yaml as file extension. If you name use tfaction.yml instead of tfaction.yaml the target is not picked up which is confusing at first.
Example Code
No response
Note
I guess you would need to think about situations where you have a tfaction.yml and a tfaction.yaml in the same folder
The text was updated successfully, but these errors were encountered:
Thank you for your feedback.
I think you can change file names with the environment variable TFACTION_CONFIG and the configuration working_directory_file.
We had the issue that we did use .yml and had to search a while and read code to figure out what our problem was. We now changed to yaml and everything works.
The feature request was more about helping others in the same situation by either reading both files or maybe give an error or something?
Feature Overview
Allow .yml file extenstion for tfaction and tfaction-root config files
Why is the feature needed?
YAML files can have .yml or .yaml as file extension. If you name use tfaction.yml instead of tfaction.yaml the target is not picked up which is confusing at first.
Example Code
No response
Note
I guess you would need to think about situations where you have a tfaction.yml and a tfaction.yaml in the same folder
The text was updated successfully, but these errors were encountered: