Closed darkpixel closed 6 months ago
Stuff is being tossed out in the 3008 release, 3007.0 is similar to 3006 and was just released. Improvements to the tool gladly welcomed in a PR with tests, it is community driven after all.
Gotta love the Saltstack model. We're kicking a bunch of useful stuff out of core, go use this tool that's unsupported and hasn't worked properly in at least 6 months. If you don't like that it's broken, feel free to code it yourself.
I have a ton of code for managing large standardized networks of Windows machines and protecting virtualized environments from cryptolocker, and handling the security of those networks. I even built a module and web interface for gathering data from minions to generate reports, alert on out-of-date software and other security issues.
I'd love to release it (and support it) so the community can benefit from it, but I don't have time to constantly fight all the broken Salt infrastructure around releasing it. I don't have time to do both. I guess I'll take another look when 3008 lands.
@darkpixel Rather than If you don't like that it's broken, feel free to code it yourself. , I was actually requesting that if there are bugs, please give us fixes, given the Salt Core Team got hit bad with the Broadcom acquisition, the team is stretched badly, and needs help from the community on plugging the holes when they are found. See https://github.com/salt-extensions and the Salt-Extension Working Group on https://saltproject.io/working-groups/
I get that things are crazy after the acquisition. I have zero clue about issues in setuptools-scm. Never used it. Never used setuptools. I'm trying to plug a hole for a group of users who manage Windows networks and virtualized environments, I don't have time to learn the intricacies of setuptools, so I can't give you a fix.
@darkpixel Not a problem, just wanted to explain where the team was coming from, needing any help it can get. @twangboy will have to step in and resolve the windows issues. :)
No worries, but just to clarify, I'm not running this on Windows. I'm a Linux and BSD user, but I support a lot of people who make the bad decision to use Windows. ;)
I thought I'd take another stab at turning a few modules I've written into a salt-ext.
I installed the latest version of salt-extension via
pip install --upgrade salt-extension
and it installed version0.24.0
.I created followed the instructions...then realized 0.24.0 was old and there have been ~15 commits since then to fix bugs.
A new release needs to be cut or the instructions should be modified to tell users to just install from HEAD.
pip install git+https://github.com/saltstack/salt-extension.git
I then ran:
Oops. I ran that from my 'code' directory thinking it would create 'cait-salt'. Nope. It littered my code directory with a ton of files and directories instead of warning that it was about to operate on a non-empty directory.
zfs rollback
to the rescue.Created cait-salt, cd'd into it, and re-ran the command. It helpfully spit out some instructions for me:
...so I followed the instructions:
It's frustrating that the tool released for de-cluttering salt core is so janky while stuff is already being tossed out of core in the new 3007.0 release.