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
[master] Initial purge of community extensions #65971
Conversation
Things that seem useful to keep in core (esp. sqlite modules, nacl modules, pkg runner, aptpkg/denconfmod states, rsync state):
Alternatively, what is the process to get them back into core, if there is a significant demand? |
a4dd4af
to
18b4347
Compare
18b4347
to
04189d1
Compare
- Add back cmd_json and cmd_yaml pillars for test fixes - Remove broken tests and bump cache seed - Fix filemap - Restrict pyzmq to <25.1.1 - Fix pkg tests - Fix performance test - skip tests that failed due to zypperpkg module removal - Fix tmp path so test passes on windows - Remove files accidently added
8d5c330
to
7a0e8cc
Compare
At this point it's very unlikely that anything removed by this PR will get added back in. If there is anything out of this list that is useful then there should be sufficient enough motivation for someone other than the core team to maintain a salt extension. Even if something is deemed to be worth of being supported further by the core team. We'd make an extension rather than adding it back into Salt. The one outlier I can think of would be we find a significant bug caused by something that has been removed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I
Hi @dwoz , what would be the tentative timeline for 3008 release? |
What does this PR do?
Initial purge of community extensions for 3008
#65970
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.