Hello! Thank you for submitting a Salt Enhancement Proposal! Our process is detailed in theREADME.md and more about theSEP Life-cycle. An Open Core Team member will be assigned to follow up and help guide this SEP soon and you will find the this in the Community Slack channel #sep.
Please be sure to review ourCode of Conduct.
You can also check out some of our community
resources:
-Community Wiki
-Salt’s Contributor Guide
-Join our Community Slack
-IRC on LiberaChat
-SaltStack YouTube channel
-SaltStackInc Twitch channel

This will be SEP 36 - feel free to update your filename/file contents 👍

👍 from me. I think it's a great idea, and it seems like something that would be straightforward to implement. The main risk that I see is around the config, as you called out in the SEP. We definitely have native minions that would have different compression tools available, but if we could use some kind of targeting similar to the way we do with top files, in theory that should solve the problem.

Itmay be possible that we have to ship that information alongside the thin, but I'm not positive, having not looked closely at that code lately 🙃.

I think it would be 100% possible to build up this functionality in layers - if we start with just allowing support for any of the built-in compression, we could merge that in and then work up to whatever alternative approaches we need.

Apologies for the long hiatus, we're working to refocus on getting SEPs through the process.

To summarize:

No objections have been made, a few possible approaches were mentioned. Given the gap, after next week we'll go ahead and put this into final comment period.