In this case only the patch definitions (installer versions) should be automatically linked. The final patch policy to deploy the patch to the clients will be managed by hand. This is useful for admins who want more control over the deployed version.
This patch doesn't brake any existing workflows nor does it add a new variable. If no patch template is provided, no patch policy will be created. The user get's informed about this behavior, and it's also addressed in the summary:
[...]
JamfPatchUploader: No patch template provided. Patch creation will be skipped and only installers will be linked.
[...]
The following patch policies were created or updated in Jamf Pro:
Patch Id Patch Policy Name Patch Softwaretitle Patch Version
-------- ----------------- ------------------- -------------
0 Not created - missing template Mozilla Firefox 107.0.1
I've updated also the README. I hope it's okay to create a direct pull request :)
Like requested in https://github.com/grahampugh/jamf-upload/issues/63 there are patching workflows without the need for constant up to date patch policies.
In this case only the patch definitions (installer versions) should be automatically linked. The final patch policy to deploy the patch to the clients will be managed by hand. This is useful for admins who want more control over the deployed version.
This patch doesn't brake any existing workflows nor does it add a new variable. If no patch template is provided, no patch policy will be created. The user get's informed about this behavior, and it's also addressed in the summary:
I've updated also the README. I hope it's okay to create a direct pull request :)