-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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] Distribute saltexts in salt-ssh thin package #66522
Conversation
This is an unpolished proof of concept of how to distribute Salt extensions together with the thin package.
@max-arnold You might be interested in this. It would be awesome if @s0undt3ch could leave a comment [since you're probably the most knowledgeable in this domain :)]. |
Cool, thanks for tagging me! Didn't test your changes yet (will have some time next week), but there are two features this might potentially interfere with (i.e. worth checking):
Also, are there any downsides of enabling this flag by default? I guess this can be done via Saltfile if someone doesn't want to always specify the CLI flag, but maybe this option being True by default will result in a better experience out of the box? |
Thanks for answering :)
Two (likely minor) issues that come to mind are a) a minor processing overhead b) possibly some issues where new libs are introduced into an environment that weren't there before. Note: Since
If enabled in the master opts, it should work.
min) This does not touch |
I too have no idea what |
What does this PR do?
Adds packages that provide a
salt.loader
entrypoint to the Salt-SSH thin archive.What issues does this PR fix or reference?
Fixes: #66559
(marginally related: saltstack/salt-bootstrap#1975 https://gitlab.com/saltstack/pop/heist-salt/-/issues/9 https://gitlab.com/saltstack/pop/heist-salt/-/issues/73)
Previous Behavior
No way of using Salt extensions via Salt-SSH
New Behavior
Salt extensions can work via Salt-SSH
Merge requirements satisfied?
Commits signed with GPG?
Yes
Additional context
Definite issues:
Possible issues:
entry_points.txt
file stats are not set at all (we could just include the file itself if the filtering is unnecessary, but I'm not exactly sure how to get the absolute path to it without accessing an internal attribute)I don't think this has any security implications since the modules are loaded on the master anyways.