jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

FR: Update Installomator to current version at run time #91

New Issue
Closed
opened 2026-01-19 18:31:30 +00:00 by michael · 1 comment
michael commented 2026-01-19 18:31:30 +00:00
Owner
Copy Link

Originally created by @fraserhess on GitHub.

I'm requesting a feature to optionally have Jamf Setup Manager download and use the current version of Installomator.sh from GitHub. This allows Jamf Setup Manager to keep up with changes and fixes to labels in Installomator without having to keep releasing JSM.

JSM should fall back to the built-in Installomator.sh if the download fails.

Originally created by @fraserhess on GitHub. I'm requesting a feature to optionally have Jamf Setup Manager download and use the current version of Installomator.sh from GitHub. This allows Jamf Setup Manager to keep up with changes and fixes to labels in Installomator without having to keep releasing JSM. JSM should fall back to the built-in Installomator.sh if the download fails.
michael added the wontfixenhancement labels 2026-01-19 18:31:30 +00:00
michael commented 2026-01-19 18:31:30 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

you can get a lot of this behavior as it is, already:

  • you can call a Jamf Pro policy with any version of Installomator (even a heavily customized one) as a policy script
  • you can use the built-in Installomator to install install the latest Installomator.sh with the installomator label, then use /usr/local/Installomator/Installomator.sh with a shell action
  • you can use an Installomator action with valuesfromarguments to download a completely customized Installomator installer pkg (or any other signed and notarized pkg for that matter)
  • you can add arguments to Installomator actions to override out-of-date label variables, such as downloadURL

since there is ... er ... "overlap" between the Installomator and Setup Manager maintainer teams, the delay between a new Installomator release and a new Setup Manager release with the built-in Installomator update will be short

@scriptingosx commented on GitHub: you can get a lot of this behavior as it is, already: - you can call a Jamf Pro policy with any version of Installomator (even a heavily customized one) as a policy script - you can use the built-in Installomator to install install the latest Installomator.sh with the `installomator` label, then use `/usr/local/Installomator/Installomator.sh` with a `shell` action - you can use an Installomator action with `valuesfromarguments` to download a completely customized Installomator installer pkg (or any other signed and notarized pkg for that matter) - you can add arguments to Installomator actions to override out-of-date label variables, such as `downloadURL` since there is ... er ... "overlap" between the Installomator and Setup Manager maintainer teams, the delay between a new Installomator release and a new Setup Manager release with the built-in Installomator update will be short
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label enhancement wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#91
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?