-
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
[FEATURE REQUEST] new core grain - a grain for telling if current salt build is onedir/singlebin/system packaged python #62589
Comments
or pip-installed? |
FWIW we're currently using this in custom grain to determine whether Salt is Tiamat-bundled def _is_tiamat():
return getattr(sys, "frozen", False) although that's not really the case, in practice it's enough for us |
adding @Ch3LL as we talked about this in the past on slack |
It would be very useful if it was in the @Ch3LL would you consider this for 3005.1? After 3006 it will be less useful if onedir becomes the only supported system. |
I'm curious, what use-cases you have in mind for this grain? I.e. what would be done differently in your states or modules based on this grain? An obvious one is the |
If salt is installed with classic packaging, then people probably want to use |
Since this is a feature request, it would need to go into 3006 not a point release. There is still value in 3006 since there is still different ways to install Salt: |
I've added #64446 , but I have not been able to determine a way to programattically determine if Salt was installed and running from pip. I'm open to suggestions in the meantime while I continue to investigate. |
Is your feature request related to a problem? Please describe.
Knowing if salt the current salt build is onedir/singlebin or system python based would be useful in certain states
Describe the solution you'd like
A grain that responds with "onedir","singlebin" or "system"
Describe alternatives you've considered
custom grain
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: