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
Files inside tar should have correct file permissions and retain last modified timestamps.
Actual Behavior
If output_file_mode is set, random file perms and incorrect last modified timestamps are shown:
$ tar -xvf mytar.tgz
bundle.json
main.js
$ ls -l
total 32
--w----r-- 1 daniel users 83 Jan 1 1970 bundle.json
--w----r-- 1 daniel users 12746 Jan 1 1970 main.js
-rw-r--r-- 1 daniel users 3929 Sep 18 14:05 mytar.tgz
If no output_file_mode is set no file perms are set and incorrect last modified timestamps are shown:
$ tar -xvf mytar.tgz
bundle.json
main.js
$ ls -l
total 32
---------- 1 daniel users 83 Jan 1 1970 bundle.json
---------- 1 daniel users 12746 Jan 1 1970 main.js
-rw-r--r-- 1 daniel users 3922 Sep 18 14:03 mytar.tgz
Steps to Reproduce
terraform apply
How much impact is this issue causing?
High
Logs
No response
Additional Information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
- Preserve original file permissions when archiving
- Apply output_file_mode to archive file only
- Add parseFileMode function for consistent mode parsing
- Set default mode (0644) for content without specified permissions
Terraform CLI and Provider Versions
Terraform v1.8.3
hashicorp/archive version 2.6.0
Terraform Configuration
Expected Behavior
Files inside tar should have correct file permissions and retain last modified timestamps.
Actual Behavior
If
output_file_mode
is set, random file perms and incorrect last modified timestamps are shown:If no
output_file_mode
is set no file perms are set and incorrect last modified timestamps are shown:Steps to Reproduce
terraform apply
How much impact is this issue causing?
High
Logs
No response
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: