-
Notifications
You must be signed in to change notification settings - Fork 38
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
[1.1.1] If the same version of package exists in Jamf Pro, policies won't update correctly #184
Comments
Sorry, read that wrong. Can you provide full output please? |
I think your problem might be that |
Hi! But plist boolean values are lower case?
Which verbosity level should I use for the outputs? |
Please use |
1.1.0 output:
1.1.1 output:
|
Thanks, that's strange that it is stopping in 1.1.1 after the package even though it is properly identifying that |
I can see some differences between the logic in the |
@jlehikoinen Please can you try out Version 1.1.2, it should hopefully fix the problem. |
Based on two different Jamf Pro + AutoPkg instances, working now as expected. Thanks @grahampugh for quick fix and premium support! |
Jamf version: 10.22.1 (on-premise)
JSSImporter version: 1.1.1
python-jss version: 2.1
STOP_IF_NO_JSS_UPLOAD
key set tofalse
in recipe overrideSteps to reproduce:
Result: Policy won't update correctly with the new override information
Expected result: Policy updates correctly with new information
Workaround: Delete the same version of installer package from Jamf Pro and run autopkg again
Additional information:
If
JSSImporter.py
version 1.1.1 is replaced with the 1.1.0 version of the script, policy updates correctly.V. 1.1.0 output example:
V. 1.1.1 output example:
The text was updated successfully, but these errors were encountered: