-
Notifications
You must be signed in to change notification settings - Fork 105
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
Executable files in a PDK template do not end up as executable in the module #1224
Comments
ReproductionHere’s a reproduction case. It’s a new PDK module based on a fork of PDK templates that includes an executable file:
|
+1 on fixing this as it makes development harder since templated scripts cannot just be executed locally and work arounds for CI/CD have to be put in place. |
Hey! With tasks in the pipeline for puppet 8 readiness I don't think I'll personally have time to work on this. However! This is open source! So if anyone wants to contribute towards this feature I'm happy to assist. My only concern here is shipping around executable files could be seen as a security risk by some.. so we would need to cover that. |
Issue moved from PDK-1803
The Problem
I have a PDK template where the moduleroot/ has a folder with scripts that are marked executable.
When I build a module based on this PDK template, the validate_things.sh script does not get created as executable. Also when updating a module based on this template, the script remains not executable.
What is expected
A file that's executable in a PDK template (either in moduleroot or moduleroot_init) should be created/updated by the PDK as executable in the module.
What actually happens
Executable files are created without the execute bit set, making them non-executable.
This also happens when pdk update'ing a module.
The text was updated successfully, but these errors were encountered: