This may have been me that asked but is was there a plan to

Question

This may have been me that asked but is was there a plan to add optional encryption to archives

wide-midnight-78598 · Answer

I didn t see it in Github or in the docs and this does feel more like a deployment thing than a compilation packaging thing

hundreds-father-404 · Answer

the `archive` target type in particular

wide-midnight-78598 · Answer

In my mindset it would be around `package` or `archive` I deploy archives of `package`s and `file`s

wide-midnight-78598 · Answer

Just to transfer around between machines stick into ansible etc I have a use case where the system might be semi trusted long story so I m going to have an encrypted archive being shipped Right now pretty trivial to do after the fact just wondering how common a use case it is Probably would be better under my proposed `deploy` goal re ansible

wide-midnight-78598 · Answer

I think my plan was a small plugin to add a field to the archive target if I can rather than create a new `encrypted archive` which is just silly

hundreds-father-404 · Answer

gt I think my plan was a small plugin to add a field to the archive target you may need a new plugin hook for `package py` or the `archive` rule to let you do arbitrary post processing A dedicated target type will be faster when prototyping I generally think folks would be interested in upstreaming encryption support tho Prob depends how complex it would be for users to understand and how maintainable the code would be

wide-midnight-78598 · Answer

For sure it s not urgent for me but in the next few weeks it would be nice if I had it Some sort of composable symmetric encryption that gets chained onto the end of builds should be pretty maintainable and usable since we have all the other facilities in play already Basically just standard encryption stuff type size pw etc

wide-midnight-78598 · Answer

I ll open a ticket to not forget about it though

wide-midnight-78598 · Answer

busy-vase-39202 · Answer

Thank you