-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force file mode inside archive #53
Comments
Hello @Supermathie our apologies for not responding sooner. It appears this issue, #10 #58 #34 are all related. It appears the permissions being misset across operating systems is problematic for a number of reasons, but a popular one being #34 . Yes we would be willing accept a PR enhancing the provider with the ability to force file mode within the archive. There have been similar attempts in #41 and #47. We would certainly review a pull request with this enhancement, but understand you may have moved on or simply don't have the spare time. Regardless if a community member manages to submit a PR or not, we will try and have this option implemented. Thank you for your contributions to the Terraform Ecosystem. |
Note: We now correct the permissions in the wrapper Makefile. |
The workaround in #90 has been released in terraform-provider-archive v2.2.0. If |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
We've discovered that the file mode of source files is now preserved by
archive_file
. While we recognize everybody has different requirements, we think it would be useful to be able to specify a mode for files either for the entire archive or for a singlesource
.Especially given how often this seems to rear its head. Would you welcome a PR on this?
Terraform Version
Terraform v0.12.12
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
(can provide)
Expected Behavior
The sha256sum of the generated zipfile is consistent across machines. This seems to be the expectation implied by #10.
Actual Behavior
The sha256sum of the generated zipfile differs depending on the mode of the source file in the archive.
Steps to Reproduce
0644
(it has a umask of 0022)0664
(it has a umask of 0002)tf plan
on both machinesThe text was updated successfully, but these errors were encountered: