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
the application executable must be in the root of the archive rather than in the /bin directory
none of the unpacked files must be world readable at any time (so they need to be stored in the tarball as 0xx0)
some of the unpacked files need custom permissions
It is not feasible to change these constraints in the short term.
As a general purpose solution, I would suggest to add some sort of mapping/callback to the create(.*)entry methods so that a filter can be injected as a setting.
I have worked this around for the pack task by scanning the target/pack directory tree and changing the permissions on the file system. Unfortunately the packArchive task ignores the filesystem settings.
At the moment I'm not able to fork/pull request.
Regards
Nico
The text was updated successfully, but these errors were encountered:
Hello,
our current deployment policy dictates that:
/bin
directoryIt is not feasible to change these constraints in the short term.
As a general purpose solution, I would suggest to add some sort of mapping/callback to the
create(.*)entry
methods so that a filter can be injected as a setting.Something like this:
I have worked this around for the
pack
task by scanning thetarget/pack
directory tree and changing the permissions on the file system. Unfortunately thepackArchive
task ignores the filesystem settings.At the moment I'm not able to fork/pull request.
Regards
Nico
The text was updated successfully, but these errors were encountered: